Software Factory is a guarded loop for coding agents. Builder agents open pull requests with an acceptance test and stop. An operator merges at a pinned commit SHA through a GitHub App limited to contents and pull requests, under a daily cap that defaults to two.
After a merge, a port-back script updates the live copy only after a shadow test passes and a dated backup is made. A 24 hour watch can restore every file if a metric or error threshold is breached. A set of Python scripts and config files carry each step.
What You Get
- A ten-step loop covering intake, blast scoring, builders, review, merge, port-back, watch and ledger
- A blast-radius score for each diff that reviewers can raise and nothing can lower
- Pinned-SHA squash merges through a GitHub App with a daily cap and optional blocked weekdays
- Port-back with a shadow test, per-file dated backups and a 24 hour restore watch
- Append-only ledgers, a not-live sweep and a daily card showing what is stuck
Common Use Cases
- Letting coding agents ship small fixes while a human controls what merges
- Putting a merge cap and rollback watch around agent-written changes to a live system
- Adding a draft-only lane for repositories where a person always merges
- Scrubbing and leak-scanning a repository before it joins the loop
What Makes It Unique
Most agent coding workflows stop at opening a pull request. This one also governs the merge and the release: merges are pinned to a SHA and capped, the live copy changes only after a shadow pass, and a restore path is armed afterward. The rules are explicit that agents never merge, never use admin flags and treat inbound text as data.
Under The Hood
The agent runs a set of Python and shell scripts from the repository checkout. They score diffs, call the GitHub REST API through a GitHub App using credentials stored in a folder you set, merge pull requests with a pinned SHA, copy files into a live directory with dated backup copies, run watchers on a schedule you start and write append-only ledger files. Reviewers are other coding agent command line tools. The SKILL.md preamble also runs two telemetry helper scripts that log usage locally and ask once about opt-in remote telemetry. Shadow tests stub sends and drop tokens from the environment, and the merge and port-back commands need an explicit execute flag.