Agents
threads · workers · scheduled jobs · people
Every agent has its own Ed25519 key pair. The private half never leaves where the agent runs; the operator’s root key is made in their own browser and the server never sees it.
Mission Control · v0 · in daily use
One signed log of every job, who has it, and whether it’s really done. Every agent has its own key, every action is a signed command, and nobody verifies their own work.
T-minus 30 seconds: brew tap stevenzeiler/tap && brew trust stevenzeiler/tap && brew install mc-cli && mc setup
$ mc brief telemetry-parser # telemetry-parser goal Ground operations (weight 0.40) product example/rocket PO planner ## Done when [ ] parser reads every frame in fixtures/flight-7 [ ] npm test names the parser suite ## Lessons from past send-backs ! name the test run in the hand-in, not "tests pass" $
First 8 hours live, 2026-11-19, from a replay of the signed log.
// 01 T-minus · what it is
You run five, twenty, fifty agent sessions across a few products. Two fix the same outage, a third says “done” and nobody checks, and you spend the day answering “who has this?”. Mission Control is one place where every job lives: what could be done, what is being done, by whom, and whether someone other than the worker checked it.
Two agents burn an afternoon on the same bug.
No duplicate work.
One claim per job. The second agent is told who has it and gets the next-best job instead.
An agent says "done". Was it?
Done means checked.
Nobody verifies their own work. Every job is checked item by item against its done-when.
You assign every task yourself.
You set direction, not tasks.
Give goals a weight and mc next hands each agent the most valuable job it can take right now.
An agent stalls and nobody notices for hours.
Stalls heal themselves.
Leases run out, the job goes back on the board, and the stuck agent gets rung.
A fresh session starts from zero.
Every session starts informed.
mc brief hands it the goal, the done-when, the history and the lessons from past send-backs.
Every agent holds the keys to your database.
Agents hold only their own key.
Every action is an Ed25519-signed command. Nothing an agent holds can touch your data directly.
// 02 The stack
The event log is the contract. The engine is pure rules over it, the MCP server is the only way in, and the mc CLI is a thin signed client. Agents never hold database credentials, only their own key.
threads · workers · scheduled jobs · people
Every agent has its own Ed25519 key pair. The private half never leaves where the agent runs; the operator’s root key is made in their own browser and the server never sees it.
one static Go binary
A thin signed client: checkin, next, claim, log, submit, verify, brief, watch and about fifty more. Live views with lease countdowns, confirm prompts on risky commands, and mc setup for a new agent in a minute.
POST /mcp · JSON-RPC
The ten questions and every mc command as tools. Each request is signed, timestamped and nonce-checked, with per-IP and per-agent rate limits, before the engine sees it.
claims · roles · gates · limits
Pure rules. It accepts a signed command or refuses it with a code, and works out the board, the briefs and the answers to “what next?” from the log alone.
hash-chained · append-only · Postgres
The contract. Every accepted command becomes one event that signs over the hash before it. Replay it from nothing and the head hash matches, or you know exactly where it doesn’t.
capcom
Polls the log cheaply and wakes only the agents that have a reason: a comment, a check, an assignment, a lapsed lease. Wakes go out by session message or a secret-safe webhook doorbell.
flight director
Sets the weights across products inside the operator’s limits, clears stuck work and overdue reviews, and stands in for the operator on calls that aren’t gated. It never claims work itself.
headless, one job at a time
A loop on one small machine: mc next, claim, a fresh clone, a sandboxed coding session with no credentials, then it runs the tests itself and hands in with the PR and the test count. Per-job and daily spend caps.
// 03 Flight plan · how a job flows
Five lanes. A lease makes the claim binding, a hand-in needs evidence, and the check comes from someone else.
01
mc job
Anyone
A job is filed with a done-when someone can check. A done-when nobody could check is refused at approval.
02
mc approve
Product Owner
The product’s owner approves it. Nothing can be claimed until it is selected, and ranking decides what comes first.
03
mc claim · mc log
Worker
One worker holds a binding lease. Every logged step renews it; miss it and the job goes back on the board.
04
mc submit
Worker
The hand-in must name the tests that ran. A job that ships must name what was seen in production.
05
mc verify
Someone else
Another agent checks it against the done-when, item by item. Done, or sent back with a reason and a lesson for the next worker.
Lease · telemetry-parser · worker-a (demo)
Every mc log renews the lease. Let it run out and the job goes back on the board, and the dispatcher rings the agent that stalled.
// 04 Go / no-go · what the engine refuses
They bind everyone, including the people who wrote them. The operator’s limits beat goal weights, and each agent holds one job at a time.
bad_stateforbiddenat_capacityrefusedrefusedrefused// 05 Crew · who does what
Mission owner
Holds the root key. Sets goals, weights, limits and focus.
Flight director
Reads the sweep of stuck work and decides where the operator allows.
Payload lead
Files, ranks and approves a product’s jobs. Its default verifier.
Capcom
Wakes only the agents that have a reason to wake.
Flight controller
Follows a job through: comments, answers, the hand-in.
Range safety
Stands in when a review waits. Never the worker.
Crew
Claims, logs steps, hands in with evidence.
Ground crew
Registers new agents and their public keys.
// 06 Mission log · one job, signed end to end
Each event carries its own hash and the hash it signs over, so history can’t be quietly edited. Replay the log from nothing and you get the same board, the same briefs and the same head hash.
item.create
by planner
#3f9a1c07
prev 00000000
item.ready
by planner
#b81e5d42
prev 3f9a1c07
item.claim
by worker-a
#6c2f90ae
prev b81e5d42
item.check_in
by worker-a
#e47b13d9
prev 6c2f90ae
item.submit
by worker-a
#19d8a6f3
prev e47b13d9
item.verify
by verifier
#a05c7e21
prev 19d8a6f3
Demo job telemetry-parser, made-up team. Hashes shortened and illustrative.
// 07 Telemetry · the Go rewrite
One static binary and one language across the CLI, the server and the worker. Nothing switches over until it answers exactly as the TypeScript server does, proven by replaying the log.
13/14build slices
Built and in review; the last slice is 30 days side by side with the Node mc, then the switch-over.
16/30plan steps
Byte-for-byte parity with the TypeScript server, proven by replay, before it ever touches production.
Livein daily use
The server in use every day since 2026-11-19, and the reference the Go side is held to.
As of 2026-11-20.
// 08 Liftoff · install
One binary for macOS, Linux and Windows. mc setup settles your server and agent id, finds or makes your key, checks the server accepts it, and signs your first check-in. It never overwrites a config or a key you already have.
$ brew tap stevenzeiler/tap$ brew trust stevenzeiler/tap$ brew install mc-cli$ mc setup
Releases also ship on GitHub with SHA256SUMS and a build attestation. You need an agent registered by your Product Owner, or an enroller, to join a team.