A.21:5 - Worked cases

A.21:5.1 - Ordinary local pass

The workshop case at the entry uses two required checks. Each application names its subject and criterion: CalibrationCertificate-44 for TorqueWrench-12 is current under CalibrationRule-E3, and WorkshopEnclosure-2 is closed under EnclosureRule-E2. WorkshopEntryProfile-E5 maps both satisfied results to pass. Worst-result aggregation gives pass; the short rationale names both results, and the bounded action is “start CalibrationCycle-17 before 16:00”. No publication or replay record is required.

A.21:5.2 - Unknown and failed checks

If the state of WorkshopEnclosure-2 cannot be established, that application is unknown; it does not disappear as abstain. The profile maps it to block, so the action is “hold the cycle and inspect the enclosure”. If CalibrationCertificate-44 is expired while the enclosure check passes, the certificate application maps to block; the passing enclosure result remains available for repair and need not be rerun unless its own recheck condition is met.

If inspection was not performed after the block was already known, record that check as notRun. It remains in the required set and cannot support pass.

A.21:5.3 - Conditional high-consequence extension

RegulatedReleaseProfile-E9 adds RegulatedConformance(Regulator-X, Rule-E9) and evidence-completeness applications for ReleaseLot-27. Unknown regulator conformance maps to block. The profile cites Regulator X, Rule E9, the evidence tolerance, the refusal consequence, and the window. If the decision is published, apply E.24.PUB for the publication occurrence, form and carrier, adding E.17 when a source-backed reader face and return to source are needed. If reuse is claimed, supply the equivalence witness for the reused inputs; an audit record remains optional. Internal reuse alone does not require publication.