Arcs
Some stories don't fit inside one series. An arc is a sequenced path across posts, sometimes across several series, meant to be read in order.
7 posts
One week, one question: can a 24GB laptop running only local models safely fix real code? The honest answer went from "it cannot produce a single valid patch" to "two local labs autonomously fix each other's code" in seven days, not by making the models smarter, but by repeatedly moving trust from model instruction-following to mechanical verification.
9 posts
One question, asked after a project spent 25 days producing documentation and no working code: why does a factory that can build individual tools still struggle to coordinate them into one real product? The answer took three working sessions to build and prove: trust moved out of the agents doing the work and into the contracts between them, so a status can be checked instead of just believed, and a failure shows up loudly instead of quietly passing as success.
6 posts
The factory's adversarial-review practice didn't start as doctrine, it became doctrine because the same failure kept recurring: a fix, itself unreviewed by a second perspective, quietly introduced the next bug. This arc is that doctrine's origin story plus four demonstrations that it holds outside its original context, closing on the sharpest evidence available: two real, live-exploit-confirmed bugs a second reviewer caught that the first pass missed.