Platform · Registry

Sealed prediction ledger

The sealed prediction registry is an append-only, tamper-evident ledger (hash-chained): every run, instance, sealed prediction, and outcome appends an entry whose hash commits to the previous one, so any edit to history is detectable. In this prototype the witness is the local chain itself; production adds an external timestamp witness.

Prototype · synthetic data — the ledger below runs locally in your browser; every record refers to generated personas and machines.
Sealed predictions

Predictions, joined with their instances

Each row is one sealed submission: the distribution was hashed and committed to the chain before the outcome existed. Statuses advance sealed → resolved → scored as outcomes and reports land.

RunInstanceSubmitterEvidence cutoffAnswer-space hashPayload hashSealed atStatus
Seeding synthetic registry…

Audit trail

Raw ledger

Every registry mutation — run created, instance registered, prediction sealed, outcome resolved, report generated — appends exactly one chain entry. The chain commits to payload hashes and identifiers only; raw distributions never enter it.

Show raw ledger entries (seq · ts · kind · payload · prev → hash) 
loading…
How tampering is detected. Each entry’s hash covers (prev_hash | payload_hash | kind | seq | ts) and chains to the entry before it. Editing any past record changes its payload hash, which invalidates that entry’s hash and every later prev_hash link — verification reports the first broken sequence number.

Data model: sealed records mirror sealed-prediction.schema.json. The witness field is prototype-local-ledger here; production replaces it with an external timestamping witness. Resolution happens on the Outcomes page; scores land on the Scoring report.