Docs

Stability

What stays put: story addresses, reference codes, issue numbers, corrections.

Story addresses
A story lives at /story/{slug}, with its markdown at /story/{slug}.md. The slug is the story’s identifier and is unique within its issue. If two issues ever carried the same slug, the address would resolve to the newer story.
Reference codes
ref is the code printed on the story’s plate, such as GB-INT-01: the section, then the story’s rank. It is unique within an issue and repeats across issues. To name a story anywhere, give the issue’s date with the ref, or use the address.
Issue numbers
number is the issue’s position among published issues, in date order. It is counted, not stored: it would move only if an issue with an earlier date were published later, or a published issue were withdrawn. date does not move. Key on date.
Publish time
The Brief publishes one issue a day, dated on the Chicago calendar. 4 issues have been published; the latest is dated 12 November 2026. Do not schedule on the clock: read date and shipped_at, which record what happened.
Freshness
/latest.json shows a new issue within five minutes of publication. The markdown files, the feeds and /v1 read the record on every request.
Corrections
A correction is added beside the story, dated; the story’s own text stays as published (Standards). A corrected story carries corrections, oldest first, in these files, on its page and in its markdown. None has been issued so far. The files carry no version number: fingerprint is the SHA-256 of every headline, dek and body in the issue, and it changes if any of them does. Store it beside anything you quote, and check corrections when you fetch again.