Failure and deny paths
CA-A1 architecture record. Updated: 2026-10-05. Conceptual fail-closed behaviour — no runtime exception code. Principle: when authority, provenance or integrity can’t be established, the record is refused or flagged; the institution is never left with silently-corrupted state.
| # | Failure | Fail-closed behaviour |
|---|---|---|
| F-01 | Selection spec lacks authority | run cannot start — engine seam refuses spec not in authorised/locked; attempted run logged as divergence event |
| F-02 | Spec modified after authorisation | impossible by construction — writes to authorised spec rejected; change requires new version + re-authorisation; any bypass attempt is an audit-visible event |
| F-03 | Duplicate respondent | dedupe policy applies at custody; unresolved duplicate → record quarantined from pool, event logged; selection proceeds only on deduped pool or fails |
| F-04 | Input-pool digest mismatch | run refuses — digest bound into spec/ceremony; mismatch means wrong pool or tampering; ceremony fails closed |
| F-05 | Seed/entropy mismatch | output invalid — the bundle’s declared seed must reproduce the run; mismatch voids the run record pending investigation, reserves never drawn |
| F-06 | Wrong engine/version | run refused or flagged — executed algorithmVersion outside algorithm_policy produces divergence event, not a result |
| F-07 | Reproducibility verification fails | run marked verification-failed — published bundle carries failure status; output cannot become membership transitions until resolved |
| F-08 | Selected person later found ineligible | transition selected→ineligible (or ineligible-found) with evidence + authority; replacement protocol opens under the same spec |
| F-09 | Reserve list exhausted | declared outcome, not hidden failure — spec’s replacement_policy defines next step (re-run under spec, or vacancy stands); recorded as event |
| F-10 | Unauthorised membership transition | write refused + divergence event — selected→seated without authority is structurally impossible |
| F-11 | Unauthorised agenda alteration | write refused; version history preserves prior text; attempted alteration logged with actor for adjudication |
| F-12 | Evidence conflict undisclosed | item flagged contested; presentation blocked until disclosure resolved; late-discovered conflict → new event + review path, record never silently edited |
| F-13 | Wrong electorate/quorum for decision | decision event invalid — electorate snapshot is bound at open; mismatched quorum result cannot close; flagged for re-decision under correct snapshot |
| F-14 | Edit attempted on closed recommendation | write refused — text frozen at closure; only new versioned recommendation objects possible |
| F-15 | Receiving authority edits recommendation | write refused — authority scope doesn’t cover recommendation text; attempt logged as authority-divergence |
| F-16 | Response deadline missed | overdue computed state; institution may declare no-response record — obligation stays visible, nothing auto-closes |
| F-17 | Implementation claimed without evidence | commitment stays self_reported/unverified — verified requires evidence_refs; claims without them are visible as unverified |
| F-18 | Permission exists but authority doesn’t | the dual-attribution test fails → flagged divergence; technical success is recorded as an authority gap, never as an authorised act |
| F-19 | External integration unavailable | seam degrades to OFF-001 manual path — canonical events still recorded; institution remains operable |
| F-20 | Stale external data | cached/imported artefacts carry fetched_at + digest; staleness threshold exceeded → flagged, never silently refreshed into canonical records |
| F-21 | Privacy retention deadline breached | deletion-overdue flagged as compliance event; affected records quarantined to minimum access pending deletion event |
| F-22 | AI-derived material submitted as authoritative | refused — ai_artefact records cannot satisfy authority/authoritative fields; submission logged |
| F-23 | Offline record conflicts with digital record | conflict record created; digital does not auto-win — adjudication event required; offline acts carry equal canonical weight by design |
Invariants
- Fail closed means fail visible: every refusal/flag produces a record — the audit trail must show the anomaly, not hide it.
- Nothing repairs in place: corrections are new events/versions preserving the failure history.
- Authority gaps are never auto-fixed: software flags; institutions adjudicate.