Search
Posts
Make the Guard Prove It Can Fail
A guard with no reachable red path is not a guard. Four gates in one day whose verdicts were decoupled from the thing they claimed to measure.
ReadSeventeen Spellings of the Same Number
A checker that governs published skill counts must discover them without hardcoding variable names. Every commit found a new legal spelling to handle.
ReadExit Zero Can Lie; Stdout Holds the Answer
A CLI can print its diagnosis to stdout and still exit 0, where a handler watching stderr never sees it. Three days of cron packets said nothing about why.
ReadFive AARs and a Count That Blinked
Filing is the unit, the receipt is the artifact. Five AARs closed Epic 2 docs governance slices, and one count correction needed a second edit.
ReadFour Slices, One Shape
Four repos on one day, each shipping a slice, each filing the AAR before the next one started. The pattern that is starting to recur on its own.
ReadCut What Was Not Earned
Four repos, one habit: an artifact has to earn its claim or it gets cut. The day was mostly the cutting.
ReadSix Systems Reporting Nothing
When the reporter cannot report. A health check that lied, a ledger with no writer, and a lint gate that ran on nothing. Six systems, same defect class.
ReadEvery Fix Failed in the Shape of the Bug It Fixed
An invariant guarded by adjacent checks is only as honest as the checks. Seven commits of corrections, then it moved into a schema that refuses the claim.
ReadA Dead Socket Is Not a Dead Host
When two facts share one value, the signal cannot tell them apart. A socket race is not a host failure.
ReadThe Agent's Mistakes Were the Fast Ones
Six agent failures on a self-hosted team relay. Five traced back to a rule I wrote down and never made anything actually enforce.
Read