Notes
Working in public, including the gaps.
Short essays about the operating model: what we count as evidence, what a gate costs, and why the site publishes rows with nothing in them.
All notes
A QA capture is not traction
Three layers of proof — surface, flow, demand — and why the site only claims the first two.
Read →
Why we publish the gap
Publishing what is not proven is cheaper than defending it later. The case for a ledger with empty rows.
Read →
The real cost of a gate
Gates delay launches and kill features. That is the point, and the bill is larger than most teams admit.
Read →
Why this exists
A build log is a gate with a date on it.
A site can describe a method forever. A note has to land on a day, make a claim, and survive being read later. That is the point: it is harder to lie in a log than in a deck.