Seven specialized services working in concert to turn natural language goals
into deployed, reviewed, production software — autonomously.
Each service owns a distinct responsibility in the factory pipeline.
The command center. Queen routes incoming goals to the right workers, manages project state across the factory, coordinates gates and approvals, and maintains the authoritative view of what's running. All other harnesses report to Queen.
The muscle. Nate Worker runs up to 10 concurrent Claude CLI instances, each working in an isolated git worktree. Auto-scales to 3 overflow workers when the queue backs up. Every task runs in its own branch — parallel, isolated, reviewable.
The architect. Given a complex goal, Nate Planner decomposes it into 3–8 atomic subtasks, estimates complexity, assigns models (haiku for boilerplate, sonnet for features, opus for architecture), and creates a git worktree per task before handing off to the Worker.
The Swiss Army knife. STI executes Claude Code skills, exposes the project registry API, handles the Cloudflare Pages deploy endpoint, and serves as the bridge between the SSOT filesystem and the rest of the factory. Also the front door for /queen-do commands.
The gatekeeper. Human-in-the-loop approval workflow for high-stakes actions. Before a deployment ships, before a branch merges, before credentials change — Dispatch Review creates a gate, waits for human sign-off, and only then lets the pipeline continue.
The clock. All cron jobs and timed triggers live in n8n — never in shell scripts or OS crontabs. Scheduled planning sessions, batch scaffolds, nightly summaries, and recurring pipeline kicks all originate here. n8n is the only thing allowed to start factory cycles.
The ledger. Tracks all projects, tasks, and priorities from mo'na.yaml — the canonical priority queue. Exposes project status, task queues, and goal progress to Queen and other services. The authoritative source of "what matters right now."
How the seven services connect and communicate.
┌─────────────────────────────────────────────────────────────────┐
│ TRIGGER LAYER │
│ n8n (5678) — cron / webhooks / scheduled tasks │
└──────────────────────────────┬──────────────────────────────────┘
│ fires
▼
┌─────────────────────────────────────────────────────────────────┐
│ COMMAND LAYER │
│ Queen (3100) — routes goals · manages projects · tracks gates │
│ pm-service (3640) — project state · mo'na priorities │
└──────┬─────────────────────────────────────┬────────────────────┘
│ decomposes │ skill / deploy
▼ ▼
┌────────────────────┐ ┌──────────────────────────────┐
│ PLANNING │ │ SKILLS API │
│ Nate Planner │ │ STI / ssot-task-invoker │
│ (3004) │ │ (3300) │
│ goal → subtasks │ │ /queen-do · /deploy │
│ + worktrees │ │ · /new-idea · registry │
└────────┬───────────┘ └──────────────┬───────────────┘
│ queues subtasks │ deploys
▼ ▼
┌────────────────────────────────────────── Cloudflare Pages
│ EXECUTION LAYER ──────────────────
│ Nate Worker (3000) Workers · D1 · R2
│ ┌──────────┐ ┌──────────┐ ┌──────────┐
│ │ Claude 1 │ │ Claude 2 │ │ Claude N │ up to 10 concurrent
│ │ branch │ │ branch │ │ branch │ + 3x overflow
│ └──────────┘ └──────────┘ └──────────┘
└──────────────────────┬───────────────────
│ before merge
▼
┌─────────────────────────────────────────────────────────────────┐
│ APPROVAL LAYER │
│ Dispatch Review (3200) — HITL gates · human sign-off │
└─────────────────────────────────────────────────────────────────┘
From natural language goal to shipped code in five steps.
You describe what you want in plain language — via /queen-do, n8n schedule, or API. Queen registers the project, assigns it a slug, and routes it.
Nate Planner receives the goal and breaks it into 3–8 atomic subtasks. Each gets a complexity score, a model assignment, and its own git worktree on a dedicated branch.
Nate Worker picks up subtasks from the Redis queue and runs Claude CLI in each worktree simultaneously. Up to 10 tasks run in parallel, with auto-scaling overflow if the queue grows.
Before code merges or deploys, Dispatch Review creates a HITL gate. You approve or reject via the review UI. Sequential task chains wait at each gate before proceeding.
On approval, STI executes the deploy skill — pushing to Cloudflare Pages, updating Workers, or triggering whatever target the project specifies. pm-service marks the task complete in mo'na.