Documentation & Support
Technical and operational documentation for users, institutions, integrators and developers, including API guidance and support channels.
One function. Explicit trust boundaries.
Documentation connects conceptual PAR architecture to operational use, integration and support.
Every material state transition should remain attributable to an authenticated actor, an authority context, a timestamp and the evidence required to reconstruct what happened.
Documentation functions.
The domain is separated into explicit functions so status, authority, evidence and lifecycle transitions can be inspected independently.
Help
Find guided help for common access, verification, record and account workflows.
Explore →02FAQ
Answers to common questions about PAR architecture, verification, identity, evidence, privacy and access.
Explore →03Support
Submit a support request with category, severity and relevant PAR references.
Explore →04Developers
Integrate PAR through APIs, webhooks, schemas and sandbox workflows while preserving authentication, authority and evidence semantics.
Explore →05API
Programmatic access for authorized creation, lookup, verification and lifecycle operations. Endpoints shown here are interface specifications until connected to production services.
Explore →06Contact
Contact PAR for institutional, commercial, media or general enquiries.
Explore →Documentation lifecycle.
Find topic
Follow guidance
Use operational tool/API
Escalate issue
Close with traceable outcome
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.
- Identifier
- Type
- Status
- Authority
- Evidence
- Timestamp
- Relations
- History
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.