Record format
chronicle/1
chronicle/1 — the Audit layer’s first worked instance: agent-drafted news where every factual claim carries a receipt (the real sealed record it rests on, where it is served, and the digest to check it against). A claim with no citation cannot validate; verification is computed against the cited records, never asserted.
version 0.1.0 · measured 2026-10-19 from a checkout · source: chronicle
node vendor-chronicle.mjs check <file> — dependency-free; not on npmA citation is a link, never a copy: the claim carries the record’s digest and where it is served, not its contents, so a reader verifies against the record at its home. verified is never a stored field — verify.mjs computes it — and nothing publishes without a named person’s consecration.
It reseals at the source rather than trusting a served digest: fetchRecord recomputes each cited record’s sha256 from its own bytes and hands on the digest it computed. A source serving an entry whose content does not hash to its own digest is unsealed — the one thing a transparency log must never do, and invisible to anything that reads the digest field and believes it.
Edge cases — each one paid for once
The feed cites live seals, never a placeholder
The first published story replaced a draft that cited “a”×64 / “b”×64 against records that did not resolve — the “navigation shell around an empty record” the roadmap warned against. An honest verifier returns unbacked, never a pass, when a source stops serving, which is the signal the format exists to make visible.
chronicle/1 is the seed of action-ledger/1
The sealed-receipt-per-claim, computed verification and human-consecration mechanisms generalise to an audit record of what agents did; verified/trueOf/proven stay refused by name, silence is unverified and an unreadable source is unread, never zero. Naming what carries over designs the general format from a running thing rather than a whiteboard.