Nine departments.
One constitution.
In v2 the fleet was a pipeline — one supervisor, interchangeable workers, a reviewer at the gate. In v3 it's a governed organisation: 10 agent roles, 34 scheduled jobs, 20 feedback loops and the guards around them — 60 registered components, each holding one seat in one of nine departments the vault calls resorts.
What changed in v3: v2 shipped well, but every agent carried its own historical build. v3 makes the fleet legible to itself: one name, one lifecycle, one card per component, and a deterministic guardrail at write time. A pipeline became a company with a constitution. This page is the org chart; the constitution itself — naming, harnesses, the Agent Card, connectors, registers and the standards guarantee — has its own chapter: The Architecture →
Every agent has exactly one home — a resort, the vault's word for a standing department. Four form the value chain a work-item travels end to end; five cut across it, serving every stage.
The nine departments above are the org chart. What makes sixty components legible to one another — and to the fleet itself — is a shared engineering constitution: one systematic name, one run lifecycle, one card per component, and a deterministic guardrail at write time. It's a chapter of its own.
The self-change machinery is fully built — and deliberately not yet armed. Every resort runs its improvement loop in SHADOW: it decides what it would change and writes that to the change log; the weekly audit names any resort that falls silent. Nothing executes.
Why say this out loud? "The fleet changes itself automatically" is the easy claim — and the falsifiable one. The honest state is stronger: the machinery exists, is measured weekly against reality, and is held on a leash by design.
If the nine departments are how the fleet is organised, the twelve tracks are what it works on — the weekly portfolio the plan is built around. Five sharpen the fleet itself, one is the factory, six are the products it ships.
Five property tracks — the fleet, sharper
The factory + six products — what it ships
Twelve tracks · nine departments · orthogonal by design — any track can draw on any department in any week.
One resident supervisor.
Generic workers.
Reviewed on every commit.
The fleet runs around the clock. A single supervisor stays alive, watches a list of jobs, and hands each one to a worker — a blank agent that becomes a specialist role just for that job. Before anything merges, an independent reviewer checks the actual change. A weekly planning pipeline keeps it all pointed at the right goals.
The v2 shift: the old fleet ran seven separate agents, each woken on its own timetable with its own fixed prompt. v2 runs one always-on supervisor and interchangeable workers that become whatever role the next job needs — cheaper, simpler, and easy to extend. It runs on Claude Code today and is built to stay as portable as possible, aiming to run locally over time.
Work isn't random. Every week starts with a direction and ends with shipped, reviewed code. Six stages carry a goal from Michael's one-line objective all the way to the main branch.
Each role carries its own AI model, effort level, time limit and pass criteria. A worker loads one for a single job, then the result goes straight to the reviewer. The roles that do the heavy lifting:
Two more roles handle outreach and the job-market scan, off to the side of the build pipeline.
Every job is reviewed before it can reach the main branch. The supervisor captures the code before and after the worker runs, then hands the real change to a fresh, independent reviewer that judges it against the job's acceptance criteria — and writes the plain-language summary. It routes the work; it never stalls the whole fleet waiting on a person.
The supervisor handles ad-hoc jobs all day. The recurring roles fire once a day at their hour, driven by the same watchdog — including a scheduled health rating that keeps the vault honest.
A system that improves without being asked.
Every week the Weekly Review role reads the full record of what the fleet did — every report, every quality-gate result, every handoff — and files specific improvement proposals. Michael approves or rejects. The fleet that ships in week four is measurably sharper than the one that shipped in week one.
One resident supervisor.
Nine role plugins.
Reviewed on every commit.
The fleet is resident — a single warm-pool supervisor stays alive around the clock, watches a work-item queue, and dispatches each item to a worker that becomes one of nine specialised role plugins. Every worker's diff is judged by a fresh-context soft-gate reviewer before it merges: pass fast-forwards to master, concerns park the commit and ping Slack. The supervisor self-heals with no admin rights, pins its model versions, and reports every dispatch to Slack. This is agentic engineering — a coordinated system with specialised roles, defined boundaries, and a weekly self-improvement loop.
There is no cron job spinning up a fresh process per task. One resident supervisor stays alive around the clock, keeps a warm Claude process pooled for reuse, and turns each queued work-item into a worker. It survives reboots, dodges double-dispatch, and brings itself back from the dead — all without ever needing administrator rights.
claude stream handles sequential dispatches instead of paying cold-start on every task. A transport blip falls back to a one-shot run so a single work-item is never burned..claude/work-items/*.json, normalises legacy and new shapes at the read boundary, and skips anything already marked done. Success writes .done, failure writes .error — never a silent swallow.HKCU Run key starts at logon and relaunches the supervisor when its pid dies or the heartbeat goes stale — catching the hung case Task Scheduler can't, with zero elevation.A worker is not a fixed agent — it's a blank Claude process that becomes a role for the duration of one dispatch. Each role plugin carries its own model, effort, time cap, tool surface, and pass criteria. Nine are live:
Every dispatch is reviewed before it can reach master. The host loop captures HEAD before and after the worker runs, then hands the actual git diff to a fresh-context Sonnet reviewer that judges it against the work-item's acceptance criteria — and writes the human-facing summary. It's a soft gate: it routes, it doesn't block the fleet waiting on a human.
HEAD onto master (never a force push) and posts to #daily: "reviewed: pass; pushed abc1234 to master".fleet-review/<id> branch, a push-hold flag pauses auto-push, and #important gets the why. Nothing unreviewed slips to master.Resident dispatch handles ad-hoc work-items. The recurring roles fire on a date-gated cadence driven by the same no-admin watcher — each role runs once a day at its hour, detached, never spawning a worker that would race the supervisor. The Strategic Architect plans the week; the rest keep the vault and the outside world in sync.
A system that improves without being asked.
Every week, the Tuning Review agent reads the full record of what the fleet did — every sprint report, every quality gate result, every handoff log — and files specific improvement proposals back into the queue. Michael approves or rejects. The agents that ship in week four are measurably sharper than the ones that shipped in week one.