Integrity verification

Each day is sealed into the one before it with SHA-256 — change any past day and this check breaks. The data is public; verify it yourself. This page fetches the raw ledger and recomputes the entire chain, live, in your browser.

The recipe (matches the publisher exactly)

hash = sha256( prev_hash + canonical({type,date,planned,done,missed_major}) )

Recomputing the SHA-256 chain in your browser…

JavaScript is off, so the live check can't run — but the verification is still yours to do. Open /history.jsonl and, for each line, recompute sha256(prev_hash + canonical(day)): every hash must equal the next line's prev_hash, and the first prev_hash is sha256:GENESIS.

Raw, public data — /history.jsonl · /public.json

This check runs entirely in your browser via the Web Crypto API — open devtools to read the exact code that computes it. Nothing here is taken on trust.

Document attestations

The chain above proves no past day was silently edited. These rows prove the published documents are the bytes they claim to be: each is pinned by SHA-256 at a frozen tag, and this page refetches the file and recomputes its digest in your browser. Offline, the same check is shasum -a 256.

One of these documents is a Certificate of Conformance to Pre-Registration PR-001. It means what PR-001 §1 says it means and nothing more — §1, quoted whole:

“Certified” means every gate’s pre-registered checks were run on named artifacts, and the results are published as measured. It is not a safety certification. It is not a performance guarantee outside the measured envelope. It is not conformance to any external standard. A FAIL certificate is published as a FAIL.

Recomputing 2 document digests in your browser…

CERT-001 2026-09-29 · not yet recomputed

Certificate of Conformance to Pre-Registration PR-001

sha256:03068c8… tag cert-001 document raw bytes
PR-001 2026-09-25 · not yet recomputed

PR-001: Public Pre-Registration, deployment pipeline v0 (for a Certificate of Conformance to Pre-Registration PR-001)

sha256:81f371b… tag prereg-001 document raw bytes

JavaScript is off, so the in-browser rehash can’t run — the check is still yours to do. Download each “raw bytes” file above and run shasum -a 256 <file>: the digest must equal the sha256: value printed on its row. The full hashes are in /documents.json.

Raw, public data — /documents.json

The digests are recomputed from the files themselves, cross-origin, in your browser — not read back from this site. If a fetch fails, this page says so instead of showing a ✓.