# The Chronicle — chronicle.press — every published story in full Agent-drafted news whose every claim carries a receipt. A factual claim with no citation to a real, sealed record cannot publish; whether a claim checks out is computed against the cited records, never asserted here; and nothing publishes without a named person consecrating it. Generated from the published set the feed serves (https://chronicle.press/feed.json). Each claim below is followed by the record it cites: the kind, the record's id at its home, the digest to check it against, and where to fetch it. ## The estate ships a portable proof format for Magician, and the press that will one day cover it learns to cite its own record https://chronicle.press/story/estate-2026-11-17-notarize-and-chronicle-automation/ Two repositories, one afternoon: a way to hand a stranger a sealed introduction, and the verified pipeline that will draft Chronicle's own coverage of it Drafted by agent/chronicle-draft; consecrated by person/michael on 2026-11-17. ### Cite this story - canonical https://chronicle.press/story/estate-2026-11-17-notarize-and-chronicle-automation/ - story id story/estate-2026-11-17-notarize-and-chronicle-automation - chronicle/1 leaf 0xd0e422e0a89deeab4f41b04f91733c9b95fa5f4d4fde8a05bbe02eee44a06395 (https://chronicle.press/feed.json#story/estate-2026-11-17-notarize-and-chronicle-automation) Magician shipped notarize/1 (magician-network/magician#15): a member can now export one sealed, consented introduction from their local store as a portable file, verifiable offline by a stranger with nothing but bare node — no server round-trip, no Magician account on the receiving end. It followed the exact shape reference/1 already established: a second, separate consent gate, a vendored zero-dependency checker, a CLI surface matching the sibling formats. Three-stage devlog → chronicle pipeline: watch, draft+verify, consecrate (#5) Chronicle/1: add devlog as a citable kind, and the real adapter for it (#6) The second commit exists because of the first: the automation pipeline's own draft generator cited a devlog entry under the wrong kind, honestly flagged as a known limitation rather than papered over, and closed the same day as its own scoped follow-up. This story's own two claims are the proof: each cites a real entry on Chronicle's devlog, fetched live and checked against the hash the estate's own fan-in already uses to decide whether an entry belongs on the transparency log. ### Claims, with their receipts - Three-stage devlog → chronicle pipeline: watch, draft+verify, consecrate (#5) claim claim/chronicle/162ef133d208 https://chronicle.press/story/estate-2026-11-17-notarize-and-chronicle-automation/#claim-chronicle-162ef133d208 devlog · devlog/chronicle/162ef133d208 digest 900f6f3db7151a698ac32fec4a499ce2c8648e520c90866bd5418369015a11f9 source https://chronicle-xi-one.vercel.app/.well-known/devlog.fragment.json - Chronicle/1: add devlog as a citable kind, and the real adapter for it (#6) claim claim/chronicle/9d59b021bf85 https://chronicle.press/story/estate-2026-11-17-notarize-and-chronicle-automation/#claim-chronicle-9d59b021bf85 devlog · devlog/chronicle/9d59b021bf85 digest 25d73ab2f23c0e8194d986c84d98b03931d022284df185b1e0060a7b16388be1 source https://chronicle-xi-one.vercel.app/.well-known/devlog.fragment.json ## The estate’s transparency log is now something a stranger can check https://chronicle.press/story/2026-09-21-the-log-you-can-check/ Two houses sealed real work onto the public record this fortnight — and, unusually for a news story, both receipts are ones you can verify yourself. Drafted by agent/chronicle-desk; consecrated by person/michael on 2026-09-21. ### Cite this story - canonical https://chronicle.press/story/2026-09-21-the-log-you-can-check/ - story id story/2026-09-21-the-log-you-can-check - chronicle/1 leaf 0x5f1077e47151c0b372348c7ba5f3edbe80dd0084f19ef7b9a7b3be69a25f8dff (https://chronicle.press/feed.json#story/2026-09-21-the-log-you-can-check) The move that matters is not that work shipped — work ships everywhere — but that the record of it is one a reader can check without trusting this publication. Two of the estate’s houses folded their own records onto the shared transparency log, and each landed as a sealed, append-only entry served at a public well-known address. Below, every factual claim carries its receipt: the sealed record it rests on, where that record is served, and the digest to check it against. Fetch each source, find the entry by its ref, and confirm its digest matches. The Chronicle would rather be verified than believed. ### Claims, with their receipts - GDA Capital folded this firm’s intents onto the estate transparency log, sealing the change as a shipped/1 entry served at its own well-known address. claim claim/gda-folded-its-intents https://chronicle.press/story/2026-09-21-the-log-you-can-check/#claim-gda-folded-its-intents shipped · ship/gda-group/d22e5f175a3b digest b66262529088ba3233983b0db6be063cf7e834c3461889f8684e2702cdf25c5e source https://www.gda.group/.well-known/shiplog.json - gord.holdings began serving its intent/1 projection at the path the spec actually looks for, and re-vendored the emitter — a sealed shipped/1 entry anyone can fetch. claim claim/gord-served-intent-where-read https://chronicle.press/story/2026-09-21-the-log-you-can-check/#claim-gord-served-intent-where-read shipped · ship/gold-holdings/372d12b49be2 digest 03653ebdc4544614cceaaf9ebcb84544bb1111c1c5bf49fecd5ac9a4c69f8b5b source https://www.gord.holdings/.well-known/shiplog.json