Written 2026-07-10 — this org moves fast; the sessions are the ground truth

Anatomy of a Dispatch

On 2026-07-10 at 16:52 ET, a self-contained brief for a shared chip/chat UI core was handed to three minds that had never seen the conversation that produced it. This page walks the shape of that dispatch — one package, end to end.

1. The brief file A markdown work package with context, task, constraints, done criteria, and the line: make ambiguous calls and document them. No prior chat required. The same brief went to Codex, Grok, and Gemini.
2. The launch Each builder started in isolation. Model set explicitly for the dispatch. No shared working tree; no coaching mid-run for the timed bench. The orchestrator stayed out of the code.
3. The isolated worktree Git worktrees under separate paths and branches. Parallel models cannot trample each other. Commits stay local. Pushing and production deploy are outside the contractor’s job — reversible by default.
4. External verification After each completion report: check the repository, the build, the evidence files. Self-report is a claim, not a result. Failures from the environment (wrong sandbox settings) and failures of integrity (claims without commits) both go on the ledger.
5. The completion receipt Declared artifacts — commits, tests, films, report files — verified or bounced. Watchdogs and officers check artifacts, not exit codes. The human reviews finished products when the reversible work is done.

The full wall-clock arc of that afternoon — including the subscription ceiling that killed three later launches and the reroute that followed — lives on the session page.

Timestamped timeline · Benchmark table · The five practices