Use Polygraph to run a software factory: a loop that picks up issues, implements them, reviews the work, and opens PRs, while humans define the intent and review the outcomes.
A software factory is a workflow, not a product. You don't buy one. You compose one from the tools you already use: your VCS, your CI, your issue tracker, your agent. Polygraph supplies the missing pieces: cross-repo orchestration, per-session workspaces that are cleaned up when the session is archived, institutional memory, PR and CI coordination, and adversarial reviews.
The workflow
Section titled “The workflow”Every run follows the same shape:
- Find work: query the issue tracker for tasks (e.g. issues labeled
factory). - Get debriefed: read the issue and search past sessions for related context.
- Set up repos: start a Polygraph session with the relevant repos.
- Implement: make the changes across the repos.
- Review: run an adversarial review on non-trivial changes.
- Open PRs: push branches, open linked draft PRs, and verify CI passes.
- Record: the session captures the decisions and design rationale.
- Complete: close the issue and link the session.
What to expect
Section titled “What to expect”A factory won't produce 100% of your code. It's a pattern: route the work agents can carry end to end through the factory, and keep everything else in normal sessions. Because every run is recorded, the institutional memory compounds and each run starts with more context than the last.
For the full walkthrough, including a reference script (about 400 lines) wiring GitHub, Linear, Claude, and Polygraph together, read A software factory is a workflow, not a product.