Review the record on your terms.
This guide uses the same public files shown on the Proof page. It supports an independent integrity review while keeping cryptographic-verifier claims explicit and fail-closed.
Choose a fixed artifact root.
Protected mailbox scenario
Help desk action scenario
- 01
Choose one saved scenario
Keep every check inside one artifact root. The two public records are deterministic fixtures, so every reviewer starts from the same files.
- 02
Open the manifest first
Confirm the scenario identifier, artifact paths, correlation value, and published SHA-256 value for each referenced file.
- 03
Follow the receipt sequence
Review the request, decision, execution field, and terminal outcome. The current public scenarios record a denied decision, no execution receipt, and a fail-closed terminal outcome.
- 04
Recompute file integrity
Download an artifact and calculate its SHA-256 value with an independent local tool. Compare the result with the value published in the manifest. A mismatch fails the integrity check.
- 05
Read verifier posture last
The posture file distinguishes fixed-fixture review from cryptographic verification. The public scenarios are verifier-bound and do not report browser-local cryptographic success.
- • The saved files are directly inspectable.
- • Published hashes can be independently recomputed.
- • Receipt status and correlation can be compared across the fixed record.
- • Missing or mismatched integrity evidence must fail the review.
- • A live Runtime or gateway decision.
- • Browser-local cryptographic verification.
- • A complete trust-bundle or receipt-chain verification result.
- • CAES certification or external accreditation.
Connect the record to the CAES authority trail.
Read the public CAES reference for the boundary between authorization before effect and evidence available for later review.