ZRF-LCR-0021 validation
Every gate between this deliverable and issue, with what would have to happen for each failure.
Demonstration project - no figure here describes a real facilityChanges are not saved
Why
Each gate is evaluated against the project's own records when the page renders.
Writes are validated against the engineering rules and then refused, because no database has been configured for this environment.
Gates
8
Passed
4
Failed
4
Blocking issue
3
This deliverable cannot be issued
3 gates fail. A validation page that reported a score would let somebody read “eight of ten passed” as nearly ready, when one of the two failures is a safety-critical value two documents disagree about.
Gates
| Gate | Outcome | What was found | What would fix it |
|---|---|---|---|
| Required inputs present | Fail | Functional test criteria: the control narrative has not been issued | obtain the missing input, or record a deviation |
| Source documents readable | Pass | every source document has been read | — |
| Requirements accepted | Pass | every attached requirement has been accepted | — |
| No open blocking comment | Pass | no blocking comment is open | — |
| Independent check assigned | Fail | no checker has been assigned | assign a checker who is not the author |
| Approver is not the author | Pass | no approver assigned yet | — |
| No safety-critical value in conflict | Fail | P-1201A, PT-1201, HV-3101, 12-CD-1201-150-A1A in conflict | decide which document governs on the reconciliation page |
| Template conformance | Cannot be checked | no client template has been supplied, so conformance cannot be checked | obtain the client's controlled template |
A gate nobody can check
Template conformance is reported as not checkable rather than as passing. No client template has been supplied, so there is nothing to conform to - and a gate that passes because the check was skipped is worse than one that fails, because it appears in the record as evidence.