The institutional surface for governed AI · sealed receipts only.

Receipts Registry

Sealed evidence artifacts referenced by this site. Each entry has a hash, a verification path, and a published reproduction protocol.

Receipts published

2026-05-02 · PEL Phase 1 Auditor Packet

Maturity: SEALED Aggregate tree hash: 05374f6c…814eb3

Complete, reproducible evidence packet for PEL Phase 1: implementation source (1,883 LOC), test suite (1,055 LOC, 26 tests passing), registry data (626 LOC across CTL/D-TAX/L-TAX/W-TAX), three independent evidence runs (committed success 2026-04-13, committed failure 2026-04-13, fresh live re-run 2026-05-02), and run instructions. The live re-run demonstrates the meta-control audit detecting real cadence drift on CTL-102 and CTL-200 — the system catching itself by design.

Verification: extract the packet, install pyyaml, run the test suite. Reproduction time under five minutes. Closes Auditor R5 finding P0-2.

Linked from: /architecture/pel/ verifier-state column for layers 2, 4, 5.

2026-05-02 · ARS-OMEGA Verification Suite

Maturity: DRAFTED Live evidence forthcoming

Verification script (run_ars_omega_verify.sh) and cross-VM parity check (cross_vm_parity_check.sh) for ARS-OMEGA Confidential VMs. Read-only by default. Implements the fail-loud checklist W1.1 through W6.1 against RFC v1.2 SOVEREIGN FINAL. Live evidence runs from VM-A and VM-B will publish here once Sovereign-executed via Cloud Shell.

Linked from: /architecture/ars-omega/ verifier-state table.

Receipts forthcoming

The Claim Receipt protocol

Any AI system operator who has submitted a GDTK-100 result is entitled to a Claim Receipt: a signed artifact recording the submission, the version under test, the verifier output, and the verdict. Claim Receipts are stored permanently and may be cited by the operator with the published hash.

The Claim Receipt protocol specification will publish concurrently with GDTK-100 v0.1.

No verifier, no receipt