12/05/26
The Autonomous Software
Factory Manifesto
Nobody has solved full agentic software development yet. Most agentic coding still happens with a human in the driver seat.
The Autonomous Software Factory is the production system that emerges when agents stop being chat companions and start operating inside compounding loops.
The best workflows for the Autonomous Software Factory will not be designed top-down by a vendor or imposed by a single IDE. They will be discovered by teams closest to their codebases, their production systems, and their users. What those teams need is not another prescriptive process or product. They need composable factory primitives.
These factory primitives are work packets, machine-legible repositories, isolated sandboxes, durable context, proof-of-work, observability, and feedback loops.
Autonomous does not mean opaque. It means execution happens without human line-by-line supervision; while intent, evidence, risk, and exceptions remain visible from the control room.
THE FACTORY PRIMITIVES
01
Work Packets
Issues, specs, and plans are the unit of production. The factory runs on bounded work packets: structured units of intent, context, acceptance criteria, risk, and handoff state. Every packet tells the agent what to build, what to preserve, what to prove, and where to leave the work for the next actor.
02
Agent-ready codebases
Make repositories legible to machines. Every repo should declare setup, environment, validation commands, rules, merge policy, and agent instructions. If a human has to explain how the repo works, the repo is not factory-ready.
03
Durable Context
Store memory outside the prompt. Long-running agents need durable session logs, file trails, decisions, business data, summaries, and retrieval hooks.
04
Review disappears
Behavioral proof beats line-by-line diff inspection. As agents produce more code, humans cannot remain the primary review surface. Every run must return evidence: intent, diffs, tests, screenshots, videos, previews, and the reason the factory believes the change is safe.
05
Feedback into the Harness
Every decision becomes factory memory. Runs, reviews, corrections, tradeoffs, failures, and roads not taken should harden the harness. The factory compounds when judgment stops living in chat history and starts becoming reusable infrastructure.
06
Meet Humans where they are / Bring your own interface
Software intent enters from Slack, tickets, docs, PRs, browser surfaces, and internal tools. The interface can vary; the factory underneath should remain consistent.