PROOF OF RECORD
How a receipt is made
Seraphix: Proof of Record for the AI era. Every fact, with its receipt.
PROOF OF RECORD 01 // THE CLAIM
What a Seraphix Receipt says
A Seraphix Receipt is a fingerprint of one published record. Together with the day's Record Ledger entry it makes one precise claim:
Agency X published document Y on date Z. It says Q about legal entity E. We fetched those exact bytes, with fingerprint F, at time T. Here is every change since.
The record carries X, Y, Z, Q and E, the document fingerprint F (sha256 of the bytes we fetched) and the fetch time T, exactly as stored. A correction adds a new version, so the record and its receipt change; the earlier version stays visible on the record, and the signed ledger entries that held its receipt are not rewritten.
We prove what the published record says and when; we do not certify that the record is true. If the agency's document is wrong, the receipt proves only that the document said it.
PROOF OF RECORD 02 // GATES
The nine gates a record passes before it is published
1. Source allow-list
Each record comes from a public government source on a fixed list. Its primary document must sit on that agency's own .gov host; a link anywhere else withholds the record.
2. Capture and walk completeness
Every listing is walked back to the start of the stated window. A walk that stops short, a failed page or a scan below its expected size marks the source DEGRADED. It is never shown as "no records".
3. Identity
A record attaches to a legal entity only by its exact legal name or a government identifier (CIK, UEI, LEI), or by a reviewed alias backed by a primary document. Anything ambiguous goes to a person and is not published until resolved.
4. Extraction
Every field is quoted from the document. Status is recorded as the document words it. An amount is shown only with its stated type and only when the document ties it to that entity; otherwise it is withheld.
5. Policy
No trading language. A news site is never the source of a record; A record that names an individual is published as filed and marked with a red asterisk (pertains_to_individual).
6. Four adversaries and an arbiter
Four separate checks try to break each record: a quote auditor re-fetches the source and looks for every quoted value, an identity challenger, a policy enforcer and a duplicate hunter. An arbiter applies a fixed rule table to each challenge: retract, correct as a new version, or send to a person. Anything naming an individual always goes to a person.
7. Canaries
Before each publication, deliberately broken copies of real records are fed through the checks. Each check must catch at least 95% of its own class, and zero may reach the public view.
8. Held-out check
Before a source is first published, a sample is checked by hand by a labeller separate from whoever built it. Precision must be at least 0.95 on at least 10 items.
9. Publish gate
The site re-checks the gates, the schema and the freshness limit on every request. A source that fails any of them shows DEGRADED and none of its records.
The current numbers for each source (canary catch rate, leaks, held-out precision and n, adversary outcome, last run) change with every run, so they are not restated here. They are published per source in /proof-of-record/gates.json and on the coverage table.
PROOF OF RECORD 03 // LEDGER
The Record Ledger
Every day the pipeline computes the receipt of every record in the published data files: sha256 of the record in RFC 8785 canonical JSON. It builds two Merkle trees (RFC 9162) over the sorted receipts: one over every record published at the day's last run, one over the records first seen that day. The entry holds both tree heads, the count per published file, the time it was generated and the fingerprint of the previous day's entry. It is signed with an Ed25519 key used only for the ledger.
Because each entry carries the previous one's fingerprint, changing or removing a past day breaks every later link. A day's entry may be replaced by a later run on the same day; it is final once the next day's entry links to it.
PROOF OF RECORD 04 // VERIFY
Verify it yourself
- Take the record JSON as published (for example
/r/<id>.jsonor a data file). - Open /verify and paste it. Your browser re-hashes it, checks the inclusion proof against the signed tree head and checks the signature.
- Or run the Python verifier offline (listed on /verify).
- Check the public key against DNS TXT
_seraphix-ledger.seraphixsystems.comand /ledger/pubkey.json, so you rely on neither this page nor its data alone.
PROOF OF RECORD // KEY
Signing key
- Ed25519 public key
- 4de0c75147e55c8dca81977ba49e97290825a48fa6363d85b036418eaffd1915
- Also published
- /ledger/pubkey.json and DNS TXT _seraphix-ledger.seraphixsystems.com. Check that the two agree before you rely on a signature.