ZRF-CMP-0007 validation
Every gate between this deliverable and issue, with what would have to happen for each failure.
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
Gates
| Gate | Outcome | What was found | What would fix it |
|---|---|---|---|
| Required inputs present | Fail | Commissioning sequence: the system boundary for SYS-31-01 is in dispute | 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 | Fail | 2: The system boundary for SYS-31-01 is taken from the drawn boundary on ZRF-PID-3101. The commissioning breakdown disagrees about HV-3101. | answer the comment; only the reviewer who raised it may close it |
| Independent check assigned | Pass | checked by S. Lindqvist | — |
| 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.