A field manual · July 2026
The lights are on.
Or they are off.
Software factories build code out of loops and harnesses. The hard, skilled job is deciding where each switch goes: what machines may verify alone, and where a human keeps the lights on.

The model
Three layers.
One closed system.
A factory is not a larger agent. It is an operating model: loops do the work, harnesses make their behavior bounded and observable, and a factory routes many of them through queues and gates.
FactoryQueue · orchestration · review · production
HarnessTools · sandbox · memory · gates
LoopContext → act → check → again
Fig. 01 · the unit of work moves up a level
Reading route
Six lessons, in order
Stable concepts live in the lessons. Volatile claims live in the dated snapshot and updates log, so the site can change without rewriting its foundations.
- 01The anatomyLoop, harness, factoryThe three nested units of agentic work.↗
- 02The operating modeLight and dark factoriesAutonomy levels, comprehension debt, and what “dark” actually means.↗
- 03The binding constraintThe price of the verifierBack pressure, trustworthy oracles, and why more output is not the answer.↗
- 04The outer loopWhere the human goesMove judgment upstream and automate only what has earned it.↗
- 05The dated fieldThe landscape in July 2026What is common, what is frontier, and what remains unsettled.↗
- 06From our floorDarkening a website factoryWhy dark-after-design beat dark-after-brief in practice.↗
The July 2026 position
Build light factories now. Make verification your main investment. Let narrow loops earn the dark with evidence.See how that worked in our website factory