R08 · RESEARCH RECORD · STATION · THE RECORD08 · NAV ORDER ≠ CAUSAL ORDER
I II III IV V ←→ · THE RECORD← BACKNEXT →
THE RECORD · 66 REGISTERED SOURCES
✓ CLAIMS 7e655a43…
SURVEY SHA256df4abafa…N FOR FULL HASH
PLATES SHA25687e030e3…N FOR FULL HASH
ALIAS SHA256f65e86f7…N FOR FULL HASH
MODEL JS SHA25659273fd2…N FOR FULL HASH
CLAIMS RAW SHA2567e655a43…N FOR FULL HASH
REGISTRY CANONICAL SHA25608e926f6…N FOR FULL HASH
LABELS SHA2566f93e007…N FOR FULL HASH
CULTURAL STRUCTURE SHA256d509354b…N FOR FULL HASH
VOICE MANIFEST SHA256c4b4f56c…N FOR FULL HASH
PANELS SHA2560a62f627…N FOR FULL HASH
THE VERIFICATION DOOR
Download the artifact, run the command, compare the digest. If they differ, the desk is lying — say so publicly.
RUNshasum -a 256 the-desk-claims-v0_2.json
EXPECTfe9d6970f58c6c55c1cb3b15191d6fcef72276587bd84e0c53f08f337fe573a3
EXTERNAL ANCHOR PLACED 2026-08-01 — EVERY PINNED FILE’S DIGEST IS COMMITTED TO BITCOIN VIA OPENTIMESTAMPS; THE .ots RECEIPT SITS BESIDE EACH FILE. VERIFY: ots verify <file>.ots — OR AGAINST YOUR OWN BITCOIN NODE. RECEIPTS UPGRADE TO SELF-CONTAINED PROOFS AS CONFIRMATION AGGREGATES; EACH UPGRADE IS RECEIPTED IN THE LEDGER.
EIGHT OF TEN PINNED FILES ARE FETCHABLE AT /artifacts/registry/ IN THE EXACT BYTE-FORM EACH HASH DIGESTS · CLAIMS-RAW AND REGISTRY-CANONICAL ARE PINNED INSIDE model.js AND PUBLISH WITH THE PIPELINE
P0 SURVEY & LAW — OPERATOR RATIFICATION · 2026-07-25
These three files change only by regenerating with a registry change or an operator directive, and every change is a WHAT CHANGED event. Editing them by hand is forbidden.