1. Sector execution problem
Public-sector payment systems bind consequence through eligibility determinations that become binding disbursement (or suspension), creating legal and citizen-impacting outcomes. The structural requirement is admissibility control at the moment a disbursement or suspension becomes real (T=0).
2. Consequence-binding actions
Examples of actions that bind consequence in this domain:
- payments and disbursements
- entitlements (grant / change / revoke)
- approvals and determinations
- recovery / debt actions
- access-rights changes
- contract activation for service delivery
3. Where authority can drift
Authority can drift structurally when:
- eligibility logic is treated as permission to pay (or suspend)
- decision formation and disbursement execution are separated across systems
- multiple service providers participate in execution
- evidence of why an action executed is reconstructed after the fact rather than captured at T=0
This is not a claim about any agency — it is a recurring structural condition in statutory delivery 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 (eligibility → disbursement/suspension) 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 payments or suspensions bind 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.