The estate ships a portable proof format for Magician, and the press that will one day cover it learns to cite its own record
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
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.
Every claim, with its receipt
-
Three-stage devlog → chronicle pipeline: watch, draft+verify, consecrate (#5)
devlog · devlog/chronicle/162ef133d208 Link to this claim
900f6f3db7151a698ac32fec4a499ce2c8648e520c90866bd5418369015a11f9verified against its record -
Chronicle/1: add devlog as a citable kind, and the real adapter for it (#6)
devlog · devlog/chronicle/9d59b021bf85 Link to this claim
25d73ab2f23c0e8194d986c84d98b03931d022284df185b1e0060a7b16388be1verified against its record
- verified — the digest this build recomputed equals the one the claim cites