Record Layer
Create, search and inspect PAR Records: durable references that bind an authenticated subject, an event, evidence and authority context into a verifiable state.
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.
Records functions.
The domain is separated into explicit functions so status, authority, evidence and lifecycle transitions can be inspected independently.
Search
Search PAR Records using identifiers, hashes, subject references, status filters and authorized metadata.
Explore →02Status
Records bind evidence to a subject, event, authority context and state transition. They are designed to be traceable rather than silently overwritten.
Explore →03Details
Display the authoritative record view: identifiers, subject, evidence, authority, status, relations and history.
Explore →04Create
Create a new PAR Record from authenticated subject, evidence, authority context and policy checks.
Explore →05Update
Append a controlled state transition or new evidence reference without rewriting prior history.
Explore →06Ownership
Inspect and, where permitted, manage ownership or control relations associated with a record.
Explore →07Authority
Represent an entity or mandate capable of issuing, approving, certifying or governing defined PAR actions.
Explore →Records 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.