1. Sector execution problem
Critical infrastructure binds consequence through runtime operational actions that change physical or cyber-physical state, often under tight safety and resilience constraints. The structural requirement is not just “good decisions”, but admissibility control at the moment an action becomes binding (T=0) — before infrastructure state is changed.
2. Consequence-binding actions
Examples of actions that bind consequence in this domain:
- infrastructure changes (configuration, dispatch, switching)
- access-rights changes
- safety and resilience overrides
- automated control actions
- contract activation and service commitments
- regulatory filings and incident reporting triggers
3. Where authority can drift
Authority can drift structurally when:
- optimisation signals are confused with permission to act
- multiple operators, vendors, and systems participate in execution
- operating constraints change faster than enforcement logic
- evidence of why an action executed is reconstructed after the fact rather than captured at T=0
This is not an allegation about any operator — it is a common structural risk surface in complex, real-time execution environments.
4. T=0 admissibility question
Is this action allowed to become real — right now?
5. What must be admissible
At T=0, a consequence-binding action must be admissible across the canonical vector:
- authority
- state
- constraints
- context
- evidence
6. AoR role
Architecture of Record (AoR) maps where consequence binds in infrastructure operations and where control must exist, making commit points explicit and governable.
7. SCIA Runtime role
SCIA Runtime — Stateful Contextual Integrity Architecture (SCIA) enforces admissibility at the commit boundary (T=0), ensuring operational actions occur only when authority and contextual integrity are provable, and evidence is captured at the point of commitment.
8. Regulatory / institutional relevance
This structural framing supports alignment with governance and operational risk obligations by clarifying commit points and strengthening traceability at T=0. It does not claim compliance.
9. Boundary statement
This page is a structural operating-context description. It is not an assessment, endorsement, assurance opinion, maturity model, client reference, or claim about any specific organisation’s systems.