The dev journal.
What actually happened, written the same day — including the defects found and why a fix was chosen over its alternatives. 11 entries.
Dev Journal - 2026-09-04: the demo becomes a floor, and a parallel bet asks if you could sit at the desk
One page kept getting rebuilt, twice, in the same 24 hours, and each rebuild found a real bug by actually looking at what it drew. Alongside it, a second track asked a bigger question - not "can a visitor watch Theo decide" but "could a visitor make the same kind of claim Theo do
2026-09-03Dev Journal - 2026-09-03: a second lever, a smaller deck, and the numbers stop drifting
Four threads today, in the order they actually happened: a second Coach lever for structure choice, a rewrite of the submission deck down to something a judge can actually read, a git authorship incident that turned out to be a misconfigured email pointing at a stranger's GitHub
2026-09-02Dev Journal - 2026-09-02: the loop closes, and the process that wasn't running it
The brief was the whole system at once: build the one safe self-improvement signal, then drive everything end to end, find what is wrong, and fix it without adding weight. Twelve decisions landed. The one that mattered most was not a bug in the code. It was that the code was not
2026-09-01Dev Journal - 2026-09-01: the knob, and the four places it could have lied
The ask was small enough to say in a sentence: let the user turn the risk up and down. What shipped is one config number. Almost none of the day was the number.
2026-08-31Dev Journal - 2026-08-31: legibility
The day split cleanly in two, and only in hindsight do the two halves look like the same question asked at different altitudes. The morning asked "where could this lose an unexpected amount" and answered it in code. The afternoon asked "could anyone who has never seen this system
2026-08-30Dev Journal - 2026-08-30 (third entry): from correct to legible
The first two entries today covered phase 4 (One Measure) and phase 6 (the sibling sweep) - eleven work units, ten more, twenty-one defects closed between them. This entry covers what happened after the code was done: turning a system that is now provably more correct into one a
2026-08-30Dev Journal - 2026-08-30 (second entry): the sibling sweep
Phase 6, D-095. The first entry today covered phase 4 (One Measure). This one covers what a whole-system review found afterwards, and what implementing the review found in turn.
2026-08-30Dev Journal - 2026-08-30
Phase 4, D-094: eleven work units, six defects closed, and two occasions where the measurement contradicted me rather than the code. Same convention as [2026-08-29](2026-08-29_concepts.md): the decision records carry the measurements, this is the through-line.
2026-08-29Dev Journal - 2026-08-29
One day, 60 commits, D-088 to D-093. Same convention as [2026-08-28](2026-08-28_concepts.md): this is the *concepts* journal, not a changelog - the decision records in `specs/decisions.md` carry the measurements, this is the through-line. It was also, by a wide margin, the bigges
2026-08-28Dev Journal — 2026-08-28
One day, 29 commits, D-074 to D-087. Same convention as [2026-08-27](2026-08-27_concepts.md): this is the *concepts* journal, not a changelog — the decision records in `specs/decisions.md` carry the measurements, this is the through-line.
2026-08-27Dev Journal — 2026-08-26 to 27
Two days, 37 commits, D-031 to D-049. This is the *concepts* journal, not a changelog: what we learned and why it changed the design. The decision records in `specs/decisions.md` carry the detail; this is the through-line.