Status
Records bind evidence to a subject, event, authority context and state transition. They are designed to be traceable rather than silently overwritten.
One function. Explicit trust boundaries.
Records bind evidence to a subject, event, authority context and state transition. They are designed to be traceable rather than silently overwritten.
Every material state transition should remain attributable to an authenticated actor, an authority context, a timestamp and the evidence required to reconstruct what happened.
Status lifecycle.
Authenticate actor
Bind subject & event
Attach evidence references
Validate authority
Create immutable record event
Minimum verification context.
The exact schema can vary by object class and policy version, but the verification layer should be able to resolve these core dimensions.
- Record ID
- Subject reference
- Event / assertion
- Evidence set
- Authority context
- Timestamp
- Status
- History / supersession
Designed for progressive activation.
Production status must always be sourced from the deployed service and published through System Status; this static package does not claim backend activation.