The factory
Seven stations. Every one visible.
Every step is on the board, you can review the result, and a person is at the gate.
- 1. You write what you want in the chat, from any device.
- 2. An agent plans it into tasks and builds it in its own container.
- 3. Review tests, a live preview and a recording before merging.
- 4. You approve, and it ships to production.
Station 1 · Order in
Anyone on the team writes what they want.
From the web, the desktop app or the phone. The agent answers in the same chat.
!184; it needs a person to merge.The agent is asking
Reply with a wait time when over the limit?
Station 2 · Plan and assign
The order becomes tasks on the board.
The agent breaks it into tasks, each with notes and evidence.
Station 3 · Build in parallel
Every workspace gets its own container and agent.
Many workspaces run at once, each on its own branch.
- Builder defaulttests, video, previews, merge requests
- Reviewerreads diffs, files findings under security-audit
- Opsdeploys, backups, cloud preflight
Each runs on Claude Code or Codex.
Station 4 · Quality control
Check the result before merging.
Tests, a live preview, a video and a new-user walk.
One task, one merge request, waiting on a person.
- Agent opened
!18409:48 - Recording attached to #1209:47
- 42 tests passed09:45
Station 5 · Sign-off
A person approves each merge.
Agents open the merge request. Self-merge is off unless an owner allows it.
- WaitingRate-limit uploads, 20 a minute per user!184 feature/upload-rate-limit → mainMerge
- MergedFix flaky media upload test!181 feature/media-flake → main, by sam
- MergedRelease 2.14.0release/2.14.0 → main, 3 repos, by alex
- Backendv2.14.0
- Web appv2.14.0
- Mobile appv2.14.0
One version across every repo, tagged by alex.
Station 6 · Ship
Preview, staging, production.
On AWS, a server over SSH, or DevBench's compute. Promotion follows your git flow.
- Backend apidb: appfeature/upload-rate-limit
- Web app webAppfeature/upload-rate-limit
- Worker workerdb: appfeature/upload-rate-limit
Replaced by the next deploy. Stopped when idle.
- feature/upload-rate-limitpreviewDevBench compute
- stagingstagingCloud static hosting
- mainproductionYour server, over SSH
Station 7 · Remember and repeat
What the agents learn is kept.
It goes into linked docs, and the next workspace starts from them.
Uploads now rate-limited.
- supersedesSecurity audit, week 36
- answersWho can open a shared file?
Uploads had no rate limit; recommended a per-user limit.
Sustained 20 a minute per user holds; bursts above wait within 40 ms.
- contradictsCapacity note (May)
- Nightly backup0 3 * * *ok
- Security audit, weekly0 9 * * 1ok
- Dependency bump0 7 * * 3silent run flagged
Set up with you
Start with one real project.
We set up your factory with you and ship one project from your roadmap.