The record
A fact is never edited.
Never deleted.
Every fact in the record has an identity, an append-only version chain (stated -> superseded -> corrected / redaction-decided), and a receipt on every hop it ever took. This page is how it works; the record itself is live.
01The lifecycle
The chain only ever grows.
Most databases update a row and the old value is gone. The record refuses that trade. When the world moves, the new statement links back to the one it replaced, and both stay on the chain with their receipts. What we knew, when we knew it, and the moment it changed are all first-class data.
Stated
A fact enters the record with an identity, a signed origin, and the article or instrument reading that carried it.
Superseded
The world moved: a newer statement takes the head of the chain. The old one is not erased; it is history with a receipt.
Corrected
We got it wrong and said so. The correction links the statement it fixes, and both stay readable, each with its receipt.
Redaction-decided
A challenge ran through the public ledger. The decision carries its reasons and stays visible, whichever way it went.
stated -> superseded -> corrected / redaction-decided. Every hop receipted.
Supersession is the feature. A record that admits what it used to say is the only kind you can audit.
02The posture
Published things stay published. The record moves around them.
Digests and daily editions are frozen when they ship: hash-stamped, signed, and never rewritten. When a fact cited inside one is later superseded, the edition does not change; its provenance panel says so, right at the top, and links to the fact's chain. The reader sees exactly what was published then and exactly what is known now, side by side.
Being wrong and then corrected in public is the product. Superseded counts stay on the record, worn openly, because a fact base that never changes its mind is not keeping up with the world. The posture goes all the way down: even a request to redact a fact becomes a permanent public claim on the open ledger, decided with reasons attached, whichever way it goes.
We never quietly rewrite yesterday. We publish what changed, with receipts on both ends.
03The worked example
One claim, seen by processes that share nothing.
Take a claim the record actually carries: activity on the Morpheus AI network is growing. Publishers write about it, and that lands through the news plane. Separately, our own chain instrument reads the network directly every day: sessions, staking, provider counts, signed at the moment of the reading. The claim-witness stream joins the two at claim grain, so the fact page can show both kinds of witness side by side.
The news plane
LIVEPublishers carrying the claim, counted honestly: syndication is never collapsed into fake independence. The shape is always "N publishers", never a stronger word than the data earns.
The chain instrument
LIVEMorScan reads Morpheus directly: daily session, staking, and provider readings, published as the signed morpheus_network_daily stream. An instrument no publisher operates.
Now read one for real. Every fact on the record has a literal page you can bookmark and send: open truthfoundry.ai/facts/f/3238460 and walk it top to bottom.
The statement
The fact itself, with its status on the chain: current, superseded, or redaction-decided. This is the thing you send.
Origin + receipts
Where it came from: the source fetch, the extraction, and the analysis legs, each hop hash-linked to its Ed25519 signature.
Witnesses
N publishers carrying the claim, and the claim's subjects seen by independent instruments: news, prediction markets, macro releases, internet telemetry, and chain scanners like MorScan and dTAOscan.
Lifecycle
The version chain: what the record said before, what it says now, and the dated, receipted hop between them.
The streams that carried it
The signed Data Extract API streams this fact rides in, metered per row, so anyone can pull the same data the page renders and verify the slice themselves.
The whole record browses the same way, starting at truthfoundry.ai/facts.
Grain honesty: instruments witness the subjects a claim names, never the truth of the sentence. The fact page says what each instrument reads and lets you look.
04What falls out
Statement in. Chain and receipts out.
A fact-check surface falls out of this design almost for free: hand the record a statement and get back the matching facts, their chains, their witnesses, and every receipt, instead of a model's vibe. What exists today is the record surfaces you just walked; the accuracy-report product built on them is coming. Try the early search at truthfoundry.ai/fact-check.
05Contribute
The record takes challenges in public.
Anyone can file a correction or redaction claim against a fact. The claim, the decision, and the reasons all land on an open append-only ledger. A fact that survives a challenge says so; a fact that does not stays visible as decided, because deleting the losing side is how records rot.
Challenging is one of three doors into the record: challenge it, feed it (bring a source through the ingest door, every row signed on its own path), or sign your own work on the same rails.