Software factory
A pipeline of fixed, agent-run stages that carries work items through to merged code, with a human pulled in only when a stage asks. The ZazenCodes version (Nov 2026) turns labelled GitHub issues into pull requests. Fable handles intake, Opus writes the spec and the code, a script gate runs the checks, parallel reviewers can send the work back, and an approver merges the PR or flags it for a human.
Design choices from that build:
- The first agent triages each issue. It can reject the issue or ask its author for details, and its risk rating changes later steps: for risky code the code review moves up from Haiku to Sonnet, and a medium-risk job gets a security reviewer that a low-risk one doesn't.
- Only issues carrying a
factorylabel enter, so a person chooses which issues get built. - A deterministic-spine of scripts owns job state, which makes the factory restartable after the orchestrator is killed.
- Each job gets its own worktree, branch and PR (worktree-per-task), with up to three jobs at once from one orchestrator session.
- Time and estimated cost are recorded per job, to compare jobs and tune the factory.
The zazencodes presenter names the weak spots too. Version 2 is more complicated than the first, a cheap reviewer that misreads a stronger builder's code can cost more than it saves by bouncing work back, and running it unwatched on production would be reckless.
Source: report
Linked from
Deterministic spineFeedback-loop ceilingWorktree per taskZazenCodes