Chief Agent Orchestrator
MITCH CLARKE
I build and govern fleets of AI agents that ship real systems.
TLDR
Below are the systems my agents have shipped, how the orchestration works, and the receipts. Every number on this page is real, exported straight from the runs that produced it.
The builds
What got built
Real systems, each shipped by a governed agent team. Read the plain version on the card, or open any case for the full engineering story.
ORCHESTRA
A control room for AI agents working in the terminal. You see what each one is doing and approve anything risky before it happens.
Open the case
COFFEEDEX
A field guide to coffee built for a real shop: every bean numbered like a Pokédex entry, traced to where it grew on a spinning globe, in English and Spanish.
Open the case
SLM4SMB
A private AI receptionist that reads booking emails and puts them on the calendar, running on a cheap office computer with nothing sent to the cloud.
Open the case
RTO AUDIT
An automotive training course, audited against the official standard and rebuilt from scratch: a workbook that passes, premium teaching visuals, and an AI assistant grounded in the course.
Open the case
DIAGNOSTIC BUDDY
A phone-friendly assistant that walks a mechanic from a vague symptom to the next thing to check, without needing to know how to prompt an AI.
Open the case
ORCHESTRATE
A one-command setup for a disciplined AI build: clear phases, human checkpoints, and a test that has to pass before anything ships.
Open the caseMore systems
Active
Second Brain
A Claude-native business vault with custom skills: working memory for research, workflow diagnosis, and reusable systems.
Shipped
Forgiveness Letter
A small, finished web app built in one unattended agent run. A personal one.
Open the app
Active
Pedal Builder
Design a guitar pedal in the browser and watch the circuit respond as you build. A collaboration build.
Shipped
TOMSSPYHQ
An arcade of classic and 3D browser games. Pure fun.
Play the games
How I run agents
The orchestration model
Every run follows the same structure. A boss holds the mission and never writes. A manager owns the phase sequence and the state file. Workers are disposable; they receive a brief and report back. Adversarial reviewers are always separate from the writers they review. Human gates are hard stops, not suggestions.
The map shows the structure used by the missions documented on this site.
A real governed run
A real governed agent run. An agent team scaffolds a CLI: every phase implemented, independently reviewed, then gated before commit.
Final gate: all five falsification criteria pass.
A run, documented
How a build actually goes
-
The wireframe gate passed. I issued the S2 brief to a disposable Sonnet worker: Astro skeleton, token system from the design plan, content collections wired, every page rendering real copy. The brief specified the Orchestra case page first, because that was the hardest screen. The worker had no prior context. It had the brief, the design plan, and the untouchable files.
-
The worker built the full skeleton: layout, tokens, fonts, four routes, view transitions, the claims audit. It flagged two items it was uncertain about and kept going. That is correct behaviour. I read the output before touching anything.
-
Manager verification found what the worker had partially flagged. Artifact links pointed at a GitHub remote that does not exist. A token and cost figure appeared in case copy, sourced from a roadmap file rather than a Ledger export. Both fail the falsification clause. Neither reached the published page.
-
Dead links removed. The figure withheld pending a real Ledger export. Em dashes found in source comments stripped. The amendments were committed, the build rerun, and every scan repeated from zero: dash scan, banned-word scan, locked file byte check. All clean.
-
Both manager rulings went to the copy gate. Artifact links stay out until Orchestra has a real public remote. The figure reaches the page only through a real Ledger report embed. Both confirmed. The run closed the same day it opened.
The numbers
What the runs show
This site is one of them. The numbers below come straight from a ledger my own agents built and exported, measured across every run on the estate.
Exported from real runs · 15 May 2026 to 13 Jun 2026
Operating principles
How I work
No number exists unless a tool produced it. Every figure ships from a real export or it does not ship.
Every agent runs behind a human gate. Permission decisions stay explicit, logged, and mine.
Define failure before you build. Each system carries a written test for what would prove it broken.
Whoever builds it does not review it. Review is always a separate seat.
Incidents are evidence, not embarrassments. Every failure becomes a blameless postmortem and a new control.
State lives in files, not memory. Any run can crash and resume cold from what was written down.
Get in touch
BUILD WITH ME
Got something that needs to ship under real governance? Bring it.