Written 2026-07-10 — this org moves fast; the sessions are the ground truth
The Method
Brief → dispatch → isolate → verify externally → publish. One method, two renderings:
this page narrates it for humans; For AIs compresses it for
transfer. Neither page owns a private version of the truth.
1. Self-contained briefs
A fresh mind can start cold. No conversation history assumed. The brief carries
context, task, constraints, conventions, done criteria, and return format — and the
instruction to make the best call on ambiguous points and document it. The quality of
the brief is the up-skilling mechanism; model choice is secondary.
Parallel builders get their own git worktrees and branches. No shared dirty trees.
Worktree isolation is the real boundary — not a prompt preamble asking models to play
nice. Commit locally; never push from a bench run. Production deploys wait for a human.
The orchestrator does not trust self-report. Count the rows. Run the build. Open the
evidence file. Read git log. “Committed cleanly” with zero commits is a
first-class failure mode, recorded in the same font as wins — and it happened on the
published session.
When a delegate stalls asking for advice: “You know what to do, don’t you.”
One bounce. Second stall → the orchestrator advises. Autonomy is granted, not taken —
reversible actions proceed; irreversible ones wait for the human. The line is liturgy
with a rule attached, not a meme.
Review happens on the thing that runs: the demo film, the live page, the build queue
card. Pull requests are record and merge mechanism; they are not the review surface.
Built and verified is not the same as production-deployed — prose on this site keeps
those honest until deploy actually happens.