Agent Orchestrator

MITCH CLARKE

I turn ideas into working software with governed fleets of AI agents; built for people, engineered for developers.

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.

Flagship / The Latent Space Travel Agency

Every pair of concepts has territory between them. We sell tickets.

Type two words. Travel the real geometric path between them, town by town, postcard by postcard.

In the lab

Being built right now

  • Phase 10 underway

    Prime Time Trivia

    4,693 questions, with your last 500 tracked so repeats effectively never happen.

  • In build

    prep-day

    Meal planning for Australian households; budget, nutrition, and a cook-day engine.

  • In build

    tinybrawl

    Tiny open-weight models, trained and fought in weight classes.

No links yet on purpose. Entries move up to the grid when they ship.

Featured / DAY BUILD

Seventeen skills that teach an AI how I build

A library of sharp, reusable playbooks written with Fable 5, covering the whole arc from a raw idea to a shipped product.

Explore the library

More systems

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.

Agent orchestration topology A directed graph showing the orchestration model. Boss delegates to Manager, who dispatches parallel Workers. Workers feed a Reviewer. The Reviewer reports to the Human Gate. The Human Gate approves Output. A swarm of agents flows along each connection. briefdispatchdispatchoutputoutputfindingsapproved Boss Coordinates the mission Manager Runs the phase sequence Worker A Executes one phase Worker B Executes a parallel phase Reviewer Adversarial review, never the writer Human gate Hard stop, not a suggestion Output Shipped artefact

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.

orchestrate: scaffolder build · tap to play · enable JavaScript to play

A run, documented

How a build actually goes

  1. The brief

    Gate cleared. Worker briefed.

    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.

  2. Delegation

    Worker builds. I stay out of the way.

    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.

  3. A gate fires

    Two defects. Both caught before publish.

    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.

  4. Recovery

    Amendments committed. Rescanned.

    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.

  5. Review

    Mitch confirmed both calls.

    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.

11,662,901,816 Total tokens
656 Sessions
Input 8,624,406
Output 97,645,002
Cache read 11,037,497,051
Cache write 519,135,357
Prime Time Trivia
3,985,290,847 221
Product build collaboration
1,848,692,118 23
SkillBookML
970,297,761 88
tinybrawl
872,540,646 27
Client site A
740,553,907 4
Orchestra
725,985,344 60
Portfolio site
714,680,478 88
prep-day
527,335,018 37
Personal projects
349,561,810 2
Small-model R&D
267,944,852 15
Misc shell sessions
251,434,505 9
Knowledge base
207,247,118 16
ORBIS
70,684,518 5
Internal build sprints
47,786,866 2
TOMSSPYHQ
37,774,684 1
Design system
17,657,672 1
Workflow calculator
15,387,680 1
Internal tooling and eval runs
12,045,992 56

Exported from real runs · 15 May 2026 to 13 Jun 2026 and 18 Jul 2026 to 15 Aug 2026

Instrumented runs only. Thousands of further sessions, and most of the development behind these builds, run uncounted.

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.

hello@prizmacore.com

+61 467 016 661