This chronicle opens with a short note on how it runs, because the publishing mechanism is itself the kind of small system this site exists to record.
The shape of the machine
Every long entry lives in the repository as a markdown file plus one JSON entry in a registry. The registry is authoritative: a markdown file without its JSON entry stops the build, and a JSON entry without a file does the same. Entries are ordered by date at render time, never by hand.
Briefings — the short dispatches listed under Transmissions — carry no registry at all. They publish on drop: the briefing job writes a markdown file into content/news/, a script commits and pushes, CI rebuilds and redeploys. Nothing else to do.
flowchart LR
A[markdown written] --> B[git push]
B --> C{CI build}
C -->|registry valid| D[static site generated]
C -->|registry broken| E[build fails loudly]
D --> F[Caddy serves]
F --> G[subscribers notified]
The failure mode matters more than the happy path. A broken registry must fail the build, loudly, rather than silently dropping an entry. A chronicle that can lose entries without noticing is not an archive; it is a suggestion.
What the pages can carry
Code, highlighted at build time — no highlighting JavaScript ships to the reader. A fragment of the loader that enforces the registry:
const orphans = files.filter((f) => !registry.some((p) => p.file === f));
if (orphans.length > 0) {
throw new Error(`unregistered posts: ${orphans.join(', ')}`);
}
Diagrams, as mermaid fences. They render on the reader’s machine, lazily, and only load the diagram engine on pages that actually contain one. The keyword-spotting entry carries a real example.
Images, dropped next to the entry and referenced relatively; the build pipeline optimizes them. The plate below is the site’s own survey chart:

Transmissions and subscriptions
Readers can leave an address in the footer of any page. The subscription service is deliberately small: double opt-in, a confirmation link that expires, an unsubscribe link in every message, and nothing shared with anyone. When the site rebuilds with new dispatches, confirmed subscribers are notified.
House rule, inherited from the engineering notebook this site grew out of: every number here is MEASURED, CITED, DERIVED — or labeled UNKNOWN in plain sight. That rule is older than the site and it is not negotiable.