Build4 departments · 15 agents
Autonomous delivery — spec to shipped PR
Autonomous · Always-on · One operator
The model for an autonomous AI-run business
A one-person software factory where AI agents do the building. Specs go in, production pull requests come out — clone, secure, red-team, implement, deploy, and ship, autonomously, with a human only at the approval gate.
~6 min
spec → PR (first autonomous build)
Fly.io
long-running build worker
The build engine
FORGE — the autonomous build pipeline
Every spec flows through six sequential stages. An adversarial review panel checks the work, and nothing merges until the owner approves it in Slack.
1
ANVIL
Clone, build & implement the spec
2
SENTINEL
Static security scan
3
SPECTER
Adversarial red-team
4
SPRINT
QA — unit, integration & E2E tests
5
DEPLOY
Preview / production deploy
6
PR
Open pull request on GitHub
An animated pulse traces the path each spec travels — ANVIL to PR. Then the review panel reports, and the operator decides in Slack: approve the merge, or send it back.
The workforce
The roster
A specialized workforce of 78 agents across 27 departments, organized into six divisions and conducted by JARVIS — shown in the command map below. Every department clones the FORGE pattern: a deterministic orchestrator plus scoped agents that propose and escalate, never decide unilaterally.
STUDIO also operates Creator OS — the founder’s content production line: ideas flow through a research crew that fact-checks before drafting, approved scripts render as a digital-twin video, and nothing publishes without the owner’s explicit approval flag. The factory’s content agents feed this pipeline as team members inside it — same statuses, same human gates.
The divisions
Six divisions, twenty-seven departments
JARVIS conducts six divisions; each owns its departments and clones the FORGE pattern. Explore every individual agent in the command map above.
Strategy7 departments · 21 agents
Foresight, intelligence & go-to-market
Studio5 departments · 12 agents
Content, research & the published word
Ops7 departments · 10 agents
Runs the business — reliability, cost, success
Governance3 departments · 16 agents
Risk, security & independent assurance
Life1 department · 4 agents
The owner’s personal operating system
Mission control
How the system fits together
JARVIS conducts the whole business. The six divisions find the work and draft the comms; the strongest ideas become specs in Notion; the always-on FORGE worker builds and ships them; SRE watches production — and the owner approves it all from Slack.
The factory as a platform: JARVIS conducts, the six divisions draft the specs, FORGE builds and ships, and SRE watches production — the owner approves in Slack. Individual agents live in the command map above.
Source of truth
Control plane
One linear path of authority: specs are authored in Notion, the human approves in Slack, code lands as PRs on GitHub, and changes go live on deploy.
Notion
App Specs database — the single source of truth for what gets built.
Slack
Human approval gate — the operator approves every merge, risky or not.
GitHub
Pull requests — every change is a reviewable diff, and each one merges only with the operator’s approval.
Deploy
Vercel & Fly — previews on every PR, production on merge.
Monitoring
The Admin console
A single-pane command center — health, agent activity, runs, and telemetry across the whole portfolio in one view. Open the console → (operator sign-in required).
Built on
The vendor & tech stack
The platforms that make a one-person factory possible.