Hearsay
memory space · policy pinned at
Bradbury campaign incomplete: 20/20 verified honest controls. Current verified checkpoint · offline stand below
Offline scripted hearing. Fictional claim and source.
Watch the one-minute explainer
An offline fixture walkthrough, followed by a dated Bradbury checkpoint. Live evaluation is incomplete. Film data and hashes · Open the live app.
Every number above came out of these rules, so they are published beside it. A different floor or a deeper cascade is a different space: they are fixed when the space opens and do not move for its lifetime.
The record
Every entry offered to the space, kept whatever the outcome. The misses are the more useful half.
Source carried the claim and nothing admitted contradicted it.
Unsourced, contradicted, unreadable, or turned away before a round was spent.
By class
Declared by the writer, never verified by the contract. It exists so the result is per class rather than one number.
| Class | Offered | Admitted | Rate |
|---|
Revoke an entry
The cascade is the part of this that exists nowhere else. Pick an entry, take it away, and watch what was standing on it.
Who leans on whom, and whether an entry's own source carried its claim, are both recorded in this corpus. What runs in your browser is the contract's walk over those facts: breadth-first, bounded at depth by the space policy, then a rejudge of everything tainted with the dead premise removed.
Nothing revoked.
Choose an entry to see what depends on it.
Run the gate
The half of cli/gate.py that needs no chain, running here. Everything it can settle locally is settled before a bond is spent.
Try pasting a claim that already exists with different spacing, or one containing >>>, or drop the https://.
What the judge would be shown. The marker is derived from the content, so the content cannot guess it, and runs of the marker characters inside the text are broken before it is fenced.
Verify a receipt
A verdict nobody can recompute is a verdict nobody can contest. Take a row, break it, and watch the check catch it.
Three things are checked, and each catches a different lie. The envelope hash catches a row describing a different entry. The snapshot hash catches a verdict re-attributed to another page. And the verdict is recomputed from the votes as they were cast — not from itself — which catches a row whose votes do not add up to the verdict printed beside them.
Verdict assembly lives in one pure function, implemented in both the contract and the gate and run over the same vectors by the test suite. Any row here can be recomputed from its receipt with no chain, no network and no model: python3 cli/gate.py verify --receipt r.json.
Built on GenLayer. Companion projects: Jastrow, how often validators part company on one specification, and Suborn, whether a specification survives hostile evidence.