Concepts
The consequence boundary
A consequential machine action changes money, access, rights, resources, state, custody, commitments, infrastructure or liability. ECZ-ID spans before, at and after that boundary, not only the decision.
Accountability Chain:Current stateDecisionActionReceipt
What makes an action consequential
Most machine actions are reads. The ones that matter change something that is hard to change back. An action is consequential when it changes one or more of:
- money
- access
- rights
- resources
- state
- custody
- commitments
- infrastructure
- liability
Before, at and after
ECZ-ID spans the boundary, not only the decision. Before it, who is acting, on whose authority, within what bounds and against what current state. At it, whether this action should proceed now. After it, what was recorded and whether it can be re-checked. Each item below carries its production status today.
The boundary: the action changes money · access · rights · resources · state · custody · commitments · infrastructure · liability
Before · may it proceed?
- IdentityLive · public
- AuthorityLive · signed in
- DelegationLive · signed in
- IntentLive · signed in
- Policy and constraintsCarried in the Intent
- Current stateLive · public
At · should it proceed now?
- Decision (IntentControl)Release-gated
- ALLOW
- REVIEW
- DENY
Indeterminate or unavailable: block, unless the low-consequence fail-open rule applies.
The action
Runs, or does not, in your system. ECZ-ID never executes it.
Your system
After · what can be proven?
- ReceiptNo public retrieval
- EvidenceNo public retrieval
- Historical retrievalNot publicly retrievable yetNo public retrieval
- Re-checkLive · public
Related
This page is explanation, not authority. Current state is only ever the live Resolver record. Live facts on this page were measured read-only on 2026-10-10.