← In the News

A working factory limits its questions to the human to six kinds

A Look Inside the Factory · Calvin Grunewald, ArchAstro · The Building Machine, November 19, 2026

Machine-readable Download Markdown

Grunewald built a harness, archdev, in June and added a factory mode in August. An overseer agent plans Tasks from a goal he approves and hands them to workers, each coding in its own worktree. Workers push to a private bare repository on his machine. A daemon turns each push into a durable SQLite job and runs lint, tests, policy checks and multi-agent review against the exact commit before anything reaches GitHub, then fixes review comments, CI failures and merge conflicts on the open PR. He reports that "Since August 21, the factory has merged 1,940 PRs into our monorepo."

Once the factory ran around the clock, the overseer kept blocking on him. By September 30 it had paused Tasks 67 times without telling him, and two days earlier workers had sent it 151 decision requests in about 21 hours, many of which they could have settled themselves. A question is now a paused Task with a kind, a reason and a recommended answer, and it must name one of six categories or the overseer rejects it: "The six are credentials, spending, live infrastructure (merging counts), irreversible actions, product decisions and anything the Task says needs my sign-off." For anything else the overseer decides and records why on the Task.

Review policy sits in a per-repo archdev.json rather than in the daemon, so it can be replayed against old PRs. On October 20 he ran six variants over 19 graded cases. None fixed more findings than the current config. A cheaper model cost about 3.5 times less per fixed finding, but on one case it deleted the public wrapper a reviewer had complained about. All figures are his own, from one team's monorepo, and archdev is his company's own tool.

Why it matters: The six-category list is a policy you can adopt without his tooling: make an agent name which human-owned decision it is blocked on, and let the orchestrator decide and log the rest. Keeping review policy in config, not in daemon code, is what made his replay evals cheap.