Sealed predictions · hash-committed before data arrives
The Vault
Predictions sealed before the data. Sealing is the only way to buy significance: we store the SHA-256 of your text, not the text — you can't quietly edit foresight after the fact, and confident wrongness costs you, on the record.
Seal a prediction
write it → we keep only the hash → reveal when the data lands · hash must match
“{
"P1": {
"claim": "ZERO quadruples exist among the 3 BH(6,8) classes \u2014 i.e. no 4th mutually unbiased basis of 8th-root type accompanies any of...”
revealed · text matches sha-256 e88857efba30…
no basis pinned — this seal cited no claim keys, so drift cannot be detected
contents locked — only the hash is public until the author reveals
basis drift · 3 of 5 cited claims corrected since sealing
(USR-2026-0002, USR-2026-0005, USR-2026-0008) the prediction still stands as written — a seal cannot be edited — but the registry values it reasoned from have moved
A prediction made after the data is a story. A prediction hash-committed before the data is
evidence — of foresight if it holds, of an honest miss if it doesn't. The vault records both
without editing rights, and a falsified seal outranks an unsealed boast.