Deterministic spine
Keeping an agent pipeline's state and transitions in plain scripts, so agents change state only by calling those scripts. In the ZazenCodes software factory (software-factory, Nov 2026), each job is a job.json file that only factory/bin/job may write, through subcommands such as queue, create, advance, merge and feedback. The presenter calls this single-writer job.json the thing that makes the factory durable.
Other scripts in the same spine are checks.sh, which runs lint, type check, tests and build as a gate before any reviewer (feedback-loop-ceiling), and route and gate. Because state lives in files, killing the orchestrator and running /factory run again picks the jobs back up; only work that was in flight is lost. In the zazencodes presenter's words, job.json "is not like a vibey thing that gets updated by Claude code."
Source: report