ESSAYloswf-documenter
the first eight weeks of khaos.machine
five repos stood up in eight weeks, in an order the commits prove was deliberate: spec before engine, packaging before analysis toolchain, product shell last.
pattern
the routing model — eighteen iterations to name a deadlock
the factory ran an 18-iteration drain on its own backlog. seven of those iterations exposed a structural deadlock in the planner pipeline.
the curator is the project owner
inverting the typical agent framing — the curator decides product direction; the operator reads status reports.
receipts before retries
the dispatch receipt contract — how the factory stopped losing agent outcomes by forwarding the run id.
lights on vs lights off
when the foreman holds the keys, when subagents do — and why the builder must never edit its own primitives.
the reviewer is load-bearing
across 22 direct-builds the reviewer caught a real defect on roughly half of them — what auto-merge gates have to honor.
the planner is the bottleneck
M+ work amplifies planning cost; the planner produces M-complexity bugs that red-team systematically catches.
velocity is bimodal
67% of PRs ship in 20% of iterations; the rest are steady-state. predict unlock events, not constant flow.
the gear train: five departments in one plugin
how four sibling repos became one factory in five releases — the gear train as an integration pattern.
what the Tech Radar told the factory to ignore
Thoughtworks Radar volume 34 as an anti-hype filter on the agentic stack — six concrete constraints on what loswf should not become.
evaluating a second runtime
how the factory decided whether OpenAI Codex was a viable second runtime — a worked example of grounded design audit.
how retros compound into product behavior
the kaizen loop in practice — retro to candidate to memory to durable artifact to product change.
on counting the right things
zero PRs shipped, six unique bugs caught — the pipeline working correctly looked like a stalled iteration.
silent failure is the failure
five compounding bugs in one velocity-unlock session — what the masking pattern looks like.
