Why this log exists
The atlas dates and sources other people's work. Until today it said nothing about how it was built itself, and a methodology page describes rules rather than a road.
This site is a collection of dated, sourced records about work other people did. There is a page that explains how a record is made — where candidates come from, what a date is allowed to claim, when a link may assert cause. What there was not is any account of how the thing holding the records came to exist.
That is a gap worth closing, and not only for sentiment. Most of the decisions on this project were made against a constraint that the finished surface hides: a runtime that broke in one shell and not another, a free account that answers 403 to the obvious solution, a continuous integration machine that wraps text differently from the machine the code was written on. A reader looking at the result cannot see any of that. A log can.
How it is built
Each entry is a folder under src/content/blog, holding one Markdown file per language. A translation is a file added next to the original rather than a second copy of the entry, and an entry that exists in only one language is still reachable from the other, marked as what it is — the same bargain the records make.
The entries are part of the same static build and pass the same gates. Nothing here is served from anywhere else, and nothing is fetched at read time.
About the dates
Every entry carries two of them. One is the stretch of work it describes. The other is the day the entry itself was written. The first rule this project has about dates is that an occurrence, the account of it, and the anchor a record is filed under are three separate things, and a blog is not exempt from a rule the records live by.
Every entry before this one was written today, on 20 September 2026, from the commits it describes. They are reconstructions. They are accurate as far as the repository can make them — each lists the commits it accounts for, and the numbers in them come from those commit messages and from the project’s decision journal, not from memory. But they were not kept at the time, and a reader is entitled to know which kind of document they are reading.
This entry is the only one so far whose two dates agree. It cites no commit, because the change it describes is the one being made.
Entry written September 20, 2026