1. Sector execution problem
Public-sector payments and entitlements bind consequence through eligibility determinations that become binding disbursement, legal obligation, or access to services. The structural requirement is not only policy intent, but admissibility control at the moment a payment or entitlement becomes real (T=0).
2. Consequence-binding actions
Examples of actions that bind consequence in this domain:
- payments and disbursements
- entitlement grants and revocations
- approvals and determinations
- recovery and debt actions
- access-rights changes
- contract activation for service delivery
3. Where authority can drift
Authority can drift structurally when:
- eligibility decisioning is separated from disbursement execution
- multiple systems and service providers participate in payment and delivery
- policy context changes while cases remain in-flight
- evidence of why a payment 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/entitlement) 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 entitlements 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.