Documentation
Check a receipt you can inspect, then evaluate a review. These docs explain the model and its limits.
They do not claim complete runtime truth by default.
Check a receipt first
- Open Verify a receipt.
- Choose Try an example, or paste a sample receipt JSON.
- A valid result confirms the checks named in that receipt. It does not prove the system is secure or that every underlying action was correct.
Optional package to inspect first: Public Exposure Review synthetic sample. It is not customer evidence.
Start here
Verify a receipt
Sixty seconds: open the verifier, choose Try an example, and read what valid means.
Open verifier →
Buyer path
Catalogue, sample, non-secret fit check, and what a review request starts.
Open buyer path →
How the model works
Governed execution, receipts, and what proof can and cannot show.
Learn the model →
Often needed
Browse by area
The sidebar stays small on purpose. Open a hub for deeper pages, or use search (⌘K) for education leaves and other pages not listed in primary nav.
Start
Where to begin: model walkthrough, buyer path, verify-first, and roles.
6 hubs in nav
Model
How proof works: mechanism, verification, and what receipts show.
6 hubs in nav
Operate
Running governed work: execution, governance, decisions, runbooks, scenarios.
7 hubs in nav
Reference
Commands, catalog, glossary, and external evidence mappings.
3 hubs in nav
Architecture
System-level boundaries: stack, threat model, and practices.
2 hubs in nav
Limits
- A valid public receipt result confirms the checks named in that receipt. It does not prove every underlying action was correct.
- Independent verification still depends on trusted keys and the materials you actually have.
- These docs do not claim complete runtime truth or production deployment by themselves.