Demo
From private notes to a signed page
Follow one invented project write-up through the kind of chain that guards this site: a redactor, a privacy scan that can block, a revision, an approval by one-time code, a signed ledger entry, and a check you run in your own browser.
This is a simulation. The project, the club, the planted key, the approval reply and the earlier ledger entries are all invented, and the scan uses three small rules written for this page, not the site’s own. No AI model runs here. The signing key is made in your browser when the page opens, is only a demo key and is gone when you leave. Nothing leaves your browser or is kept, and reloading the page starts again.
1. Private notes
The author’s notes for a write-up about a boat booking board built for Osier, an invented rowing club. They name the client, and a setup line holds a key. The key was planted on purpose: its letters are picked at random when the page opens, and it opens nothing.
2. Redact before drafting
The redactor swaps every key and every name on the private list for a placeholder, by fixed rules. In a real pipeline this happens before any AI model sees the text. Here nothing goes to a model: the draft in the next step is scripted.
3. Draft and scan
The first draft was written from the redacted notes, then edited by hand, and the edits brought the client’s name and the setup line back. The scan reads the finished text, whatever its history.
4. Revise and scan again
The author deletes the setup line and describes the client instead of naming it. The figure stays: it may be true, so the scan only warns, and the person who approves decides.
What changed
5. Approve with a one-time code
The request goes to the owner with a short code bound to this draft’s hash, so a reply approves exactly this text and nothing else. Here the reply is a mock: choose one.
6. Sign and verify
Anyone with the public key can check the ledger. Verify recomputes every entry’s hash from its fields, checks that each entry links to the one before it, checks every signature, and checks that each published page still has the hash its entry names.
Try to cheat
Change something, then verify again.
The published page
Ledger
Each entry names a page and the hash of its text, links to the entry before it by that entry’s hash, and is signed. 2 earlier pages are already in it.
Signed with a demo key made in this page just now, fingerprint . It is not the site’s key, and it is gone when you leave.
The demo’s scan rules
- Block:Looks like a key. The words live key or test key followed by a long run of letters and digits: the shape of a secret.
- Block:Name on the private list. A name on the private list for this story: the client, who must never be named in public.
- Warning:Figure to check. A number in a claim, such as hours saved or a percentage. The scan cannot tell whether a record backs it.
Pipeline log
Each step will appear here with its time.
What the demo shows
- Redaction before drafting. Keys and private names are swapped for placeholders by fixed rules before anything is written from the notes.
- A scan that blocks. The finished text is scanned again, whatever its history. A block cannot be sent for approval or waved through; a warning goes to the person who approves.
- Approval bound to a hash. The one-time code approves exactly one version of the text, works once, and a wrong code approves nothing.
- A signed, chained record. Each ledger entry names the page’s hash and the hash of the entry before it, and is signed, so changing any entry or any published page shows up when anyone checks.
- Checks anyone can run. Verify runs in your browser with the public key alone, and names what failed and where.
The page in this story, “Boat booking board”, is not a real project, and the club is not a real client.