The ledger
One line per card: the question it answers, the register it answers in, and a fingerprint you recompute from the artifact alone. Not a wall of green — a set of receipts. Each line says what is checkable, and hands you the value to check it against.
Every valid is paired with a deliberate control — a brake test that makes the same instrument ring — so a green is never shown alone. The control is a test we run on purpose, not an incident that happened.
verify a fingerprint in your browser
Every line below is a value you can recompute — the geometry digests recompute in your tab on the live case pages, or from the kit. Here is the one you can check right now, on this phone, with nothing sent anywhere: each receipt is a small record of a case's public verdict and digests, and it carries its own SHA-256. Recompute it in your tab and watch it match; alter one character of a copy and watch it fail.
published fingerprint ·
or download the receipt and check it on your bench:
receipt file — shasum -a 256 prints the same number.
or compute the SHA-256 of anything, yourself
Type or paste any text. The hash is computed in this tab as you type — no request is made. This is the whole idea at its smallest: a claim you can recompute is not a claim you take on trust, and the same move scales up from this one fingerprint to any record you bring.
sha256 = —
The computation is crypto.subtle.digest —
WebCrypto, built into your browser. Press Verify: nothing of yours goes out.
A verification is a number computed on your side of the glass.
the live cases — worked pages, kit on request
-
pharmacovigilance — Did the pipeline move the signal?sha256 = aec3e5db93f15e7e3d33108fb4fc24ee05f226cf6be07f78c60373b5ea07d7e0
-
model risk — Did data-prep move the protected coupling?sha256 = c1367c641b6dfe9e64cb8d62b79e22c95979ff7387c9c6e6c5e3e8c5dd7f3f10
-
AI provenance — Did the agent’s own actions leak into its record of what happened?sha256 = 67a6f95ee308a2884f73e071ed72bfb0326ba1b7d6da08a147e6ef10394009aa
-
information governance — Did a readable record shape what the system learned?sha256 = 67a6f95ee308a2884f73e071ed72bfb0326ba1b7d6da08a147e6ef10394009aa
-
privacy · right to erasure — Did the erased record actually leave the state?sha256 = 67a6f95ee308a2884f73e071ed72bfb0326ba1b7d6da08a147e6ef10394009aa
-
quantitative research — Did the backtest’s state ever see the future?sha256 = be07f3713ccc406cfd6e880a6b92dadedf6950f503e326ebc2bdfd9f897b2472
-
vendor restatements — Did the revision change the history — or only its packaging?sha256 = 150c2313632ed2bfd6600b494dbc3d24d3b4ce05bf29a442df7f488dcaa7aebb
-
authorship · AI disclosure — Which acts actually moved the record?sha256 = 5497775ca33da46a40dd3d00dbdea3e24b46c29566059aa30706d912bd198d15
The three lines that share v3 67a6f95e… — AI provenance, information governance, and privacy·erasure — are three receipts over one certified state: the same eligible agent-trace Σ, read as detection, exclusion, and erasure. The kit fingerprints differ because the kits ship different questions; the geometry digest is identical because the answer’s substrate is the same bytes.
Open items on this ledger — stated, dated 2026-07-16
One shipped kit’s verdict path carries a chosen cut, under review — its two receipts’ rating plates are withheld until it resolves. Portability beyond this architecture is written, not yet run. Four kit registers were corrected 2026-07-16 to match these pages. The reader-relative reading is not claimed — the bench that killed it is in the record. Full statement on the method page.