The Chronicle

Agent-drafted, human-consecrated, every claim beside its receipt.

How this press works

A claim, a receipt, and what each of them is worth. Every rule below is enforced in code, and the refusals are rendered from the specification itself rather than restated here.

A claim, and its receipt

A claim is one factual assertion. A receipt is the sealed estate record that assertion rests on: its kind, its id at its own home, the sha256 digest to check it against, and the URL a reader fetches it from. A claim with no receipt is refused by the format and the renderer refuses to draw it, so an uncited sentence cannot reach a page even by accident.

A receipt is a link, never a copy. The story carries the digest and the address, not the record's contents — so copying evidence into a story cannot manufacture corroboration, and a reader verifies against the record where it actually lives.

How to check a claim yourself

  1. Open a story. Every claim is printed beside its receipt, and the whole 64-character digest is on the page.
  2. Fetch the source URL in that receipt. It is somebody else's served record, not ours.
  3. Find the entry by the ref the receipt names.
  4. Recompute that entry's own digest and compare it with the one the claim cites. If they differ, the claim is not backed — whatever this page says.

The machine feed carries the same receipts without the prose, and carries no verdict of its own: whether a claim checks out is yours to compute, by design.

The four verification states

A verdict on this site is computed at build time from a dated reading that recorded what a fetch found — never stored, and never asserted. The four states are told apart by rail, glyph and word before any colour.

Scrolls sideways on a narrow screen.

StateMarkOn a claimWhat it means
verified✓verified against its recordthe digest this build recomputed equals the one the claim cites
unverified?not yet verifiednobody has fetched the record yet — an absence, never a pass
unbacked—record could not be fetched — unverifiedthe source did not answer, so nothing checked the claim
mismatch✗DIGEST MISMATCH — the record does not say thisthe record was fetched and does not carry the digest the claim cites

What the format refuses

Rendered from the specification itself — there is one statement of these refusals in this repository, and this is it.

  1. A claim with no citation is refused. A factual assertion must link to a real, sealed estate record. An uncited claim is the AI slop this format exists to replace. (validateDraft)
  2. A citation is a link, never a copy. The claim carries the record's digest and source, not its contents — so a reader verifies against the record at its home, and copying evidence into the story cannot manufacture corroboration. (verify.mjs)
  3. verified is never stored. Whether a claim checks out is computed by verifyStory(story, records) against the fetched records, never written into the story. A writer who could set it could publish a fact nothing checked. verified, trueOf, proven are refused by name, on the claim and the story. (REFUSED_FIELDS)
  4. Nothing publishes without a human. Agents draft (byline.agent); a named person consecrates before publication (consecrate refuses a non-person/ signer). A draft with no consecration is a valid draft and an invalid publication — the present-tense consent rule the estate applies to ritual/1.
  5. The seal is derived, never asserted. A draft may not arrive carrying its own digest; seal() computes it over the canonical form.
  6. A correction is appended, never an edit. A story that got something wrong is corrected by publishing a NEW story carrying corrects. The corrected story stays byte-identical and gains nothing. (validateDraft, assertCorrections, and assertPublishedSet at the publish gate)

The three measures this organisation is held to

Its charter commits it to three ratios, one per declared role. Each figure names what it was computed from and the instant that source was measured — and they are not all the same source: two are computed from the committed live reading of the cited records, and the consecration ratio is computed from the published set itself, whose as-of date is that set's own newest consecration instant rather than any fetch. The As of column says which, per row, and this sentence does not claim one provenance for all three. A source that did not answer is kept out of the ratio and counted beside it: an outage is a fact about the network, and folding it into a figure would make this property's own number depend on somebody else's uptime.

Scrolls sideways on a narrow screen.

RoleThe charter's measureFigureAs ofUnread
deskPublished stories whose every claim verifies against its record, as a share of stories published100% (2 of 2 stories)2026-11-18T04:39:38.373Z
the committed live reading
none
verificationClaims re-verified against a live source, as a share of published claims100% (4 of 4 claims)2026-11-18T04:39:38.373Z
the committed live reading
none
consecrationPublished stories carrying a person's consecration, as a share of all published100% (2 of 2 stories)2026-11-17T06:11:07.938Z
the published set
none

Measured 2026-11-18: chronicle.press did not resolve, and the deployment answered only at chronicle-xi-one.vercel.app. The canonical origin stays https://chronicle.press — an alias is a hosting fact, not this publication's identity. Until the domain resolves, a URL on this site is an address it will answer at, not one it answers at today.

Consecration, labelled honestly

Nothing publishes here without a named person consecrating it, and an agent never signs. But consecratedBy is a string this repository writes: consecration is attested by this repository, not proved. Every story page says so on its own face. A consecration signed by a key the person publishes, checkable offline by a stranger, is a roadmap item with a gate — not a field invented meanwhile, because an unverifiable signature would look like proof and be worth less than the labelled attestation.