History
Revocations
Inspect the chronological history of revocations events, state transitions, authority actions and supporting evidence.
Purpose
One function. Explicit trust boundaries.
History is a cross-domain chronology for reconstructing how an object or decision evolved over time.
Every material state transition should remain attributable to an authenticated actor, an authority context, a timestamp and the evidence required to reconstruct what happened.
Operational flow
Revocations lifecycle.
01
Resolve object
02
Load event chronology
03
Validate event integrity
04
Show supersession/revocation
05
Export verification trail
Object model
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.
- Object reference
- Event ID
- Event type
- Actor / authority
- Timestamp
- Prior state
- New state
- Evidence reference
Operational state
Designed for progressive activation.
InterfacePrepared
BackendIntegration required
Audit trailDesigned
Status modelDefined
Production status must always be sourced from the deployed service and published through System Status; this static package does not claim backend activation.
Related PAR domains