We show our receipts

The machinery that writes them: append-only hash-chained manifests, dual RFC 3161 time witnesses, pinned Ed25519 signatures, and one offline fail-closed command — receipt verify. An open-source package anyone can adopt; it has its own page.

What an offline check of agent-produced records establishes and refuses to establish, why trust anchors live in the verifier's own code, and the four evidence classes behind the package. Manuscript, PDF, and the code it describes.

Engine releases ship checksums and build attestations. Verify the binary you downloaded against the attestation log with commodity tools before you run it.

Every rule cites the provision of law it encodes and lands with a companion test. The repositories are the receipt: the citation, the test, and the history of both are public.

Encodings are compared against independent implementations in the open, and disagreements are recorded rather than resolved quietly.

Computed, not granted: the harness derives completeness and fidelity, and a node certifies itself — nobody, including us, grants it by hand. Every node wears its tier in the app, including the empty certified tier at launch. The emptiness is the credibility.