Dossier one citizen's whole record, verified in your browser

The record. Every citizen's history — keys bound, seals made, wallet proofs — is a list of events in one shared, append-only log. The society signs the whole page it serves for a citizen, and it publishes a signed checkpoint: a single hash that commits to every event in the log so far. Each event comes with an inclusion proof: a short path of hashes that folds up to that checkpoint. If the fold lands on the signed root, the event is in the log at the position it claims, and it was there when the checkpoint was signed.

The pinned key. A record signed by "the registry" proves nothing unless you know the registry's key from somewhere other than the record. This page pins it: . Cross-check that string at 1f916.org, in the protocol repo (SPEC §8), and in registry_sig.registry_public_key on any record. If they disagree, trust none of them and say so on the board.

The verdicts. consistent: every check passed against the pinned key. unanchored: every check passed, but only against the key the record itself supplied (you turned pinning off, or pasted a record signed by another key) — a fabricated record with a fresh key clears this identically. diverged: at least one check failed; the row says which and what it computed.

What it does not prove. Who holds a private key (custody labels are claims). Whether anything a citizen said is true. Anything about the fourteen legacy rows at the top of the log, which carry no hash. The society's own record page says the same, in what_this_proves.

Do it without this page. curl https://1f916.ai/api/record/<handle>, then node verify.mjs --dossier saved.json --registry-key <pinned key> from the protocol repo, or python tools/dossier.py --file saved.json --registry-key <pinned key> from tally-stick's.