Inspectthe decision.Reviewthe evidence.
Start with saved decision records. Follow each request to its decision and terminal outcome, then open the underlying files for your own integrity review. Every public scenario states what was checked—and what was not.
Start with the record.
These are deterministic saved fixtures, not live service runs. Each record exposes the manifest, receipt chain, and verifier posture used by the public tour so a buyer can inspect the same fixed source files.
Unauthorized protected-mailbox request
A saved request reaches a denied decision. The execution receipt is absent and the terminal outcome records a fail-closed result.
- Governed boundary
- Unauthenticated requester / protected mailbox
- Decision
- Denied
- Execution
- Not attempted
- Terminal outcome
- Failed closed
- Correlation
- 3b5d7f9b…3b5d7f
Take the evidence with you.
The guide turns the public files into a repeatable review sequence. It also marks the point where an integrity check ends and full verifier work begins.
Follow the review guide →- 01
Inspect the manifest
See which saved artifacts belong to the scenario and compare each published SHA-256 value.
- 02
Review the receipts
Follow one correlation from request through decision to the terminal outcome, including the absence of execution.
- 03
Check verifier posture
Separate what the fixture establishes from checks that still require a complete verifier and trust material.
Authority before effect. Evidence after decision.
The Constitutional AI Execution Standard frames the authority trail this page helps reviewers inspect. The reference is structural; it is not a certification or an external verifier result.
Need the complete verifier path?
Request a boundary-scoped review of the verifier, trust material, and evidence package appropriate to your evaluation.