Registry Layer
Navigate the authoritative PAR index of registered entities, records and evidentiary relations while preserving status, provenance and authority context.
One function. Explicit trust boundaries.
The registry makes PAR objects discoverable and cross-referenced while keeping type, status, authority and lifecycle boundaries explicit.
Every material state transition should remain attributable to an authenticated actor, an authority context, a timestamp and the evidence required to reconstruct what happened.
Registry lookup
Resolve a PAR reference and return current status together with the evidence and authority context permitted for public or authenticated access.
Registry functions.
The domain is separated into explicit functions so status, authority, evidence and lifecycle transitions can be inspected independently.
Persons
Browse or search registered persons references with type, status, authority and relationship context subject to access controls.
Explore →02Companies
Browse or search registered companies references with type, status, authority and relationship context subject to access controls.
Explore →03Authorities
Browse or search registered authorities references with type, status, authority and relationship context subject to access controls.
Explore →04Devices
Browse or search registered devices references with type, status, authority and relationship context subject to access controls.
Explore →05Assets
Browse or search registered assets references with type, status, authority and relationship context subject to access controls.
Explore →06Records
Browse or search registered records references with type, status, authority and relationship context subject to access controls.
Explore →07Relations
Browse or search registered relations references with type, status, authority and relationship context subject to access controls.
Explore →Registry lifecycle.
Resolve identifier
Confirm object type
Read current status
Traverse authorized relations
Inspect lifecycle history
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.
- Registry ID
- Object class
- Canonical reference
- Current status
- Jurisdiction / scope
- Authority context
- Relations
- History pointer
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.