Journal
One update a week, each sourced from a measurement in the tree — never a roadmap promise. Two formats: a Mechanism piece that explains one part of the system in depth, and a Finding post that reports a single measured result, including the ones that did not work.
The first entries
Each links to the record it is drawn from. These publish as the site goes live; until then, the records are already in the repository.
The adjudicator is a cascade of one
Why every judge panel we measured scored below its best member, and what a member below chance does to a majority vote.
A keyword scan beat the embedder
Six hits to four on the memory fixture, and what that says about spending a context budget on recall.
9% of the corpus was invisible
The chunker truncated long sections for the life of the index, and no index could say it was stale. How it was found and fixed.
Why a prompt has no single class
Every builder joins public instruction to private material, so the gate constructs what leaves instead of inspecting it. The design decision behind the boundary.
The rule
No post without a record behind it. A Finding reports a measurement, a Mechanism explains a part of the system that exists. Neither announces a feature that is not built — that is what the roadmap's "not proven" column is for.