Two related orchestration failures from recent runs:
1. An orchestrator missed the multi-agent concept entirely and produced
reviews / implementations itself instead of dispatching @check / @make.
The workflow described phases as "Dispatch @<name>" everywhere but
never explained who the cast was, what "dispatch" meant, or that the
orchestrator (agent: build) is distinct from the subagents.
2. Another orchestrator dispatched @test pointing at a $RUN_DIR/task-N.md
that it never wrote — the file-write instruction in Phase 5 was a
single bolded sentence inside a paragraph, easy to skim past, and
nothing checked artifact existence before dispatching.
Adds a top-level "Roles & Dispatch" section between the parse line and
Run Artifacts. It establishes the multi-agent model, lists the cast
(@check / @simplify / @test / @make / @pm) with one-line role and
permission notes, defines "Dispatch" as a tool call (not a role-play
instruction), and lists three anti-patterns the orchestrator must
avoid (acting as a subagent, skipping a dispatch, paraphrasing
artifacts instead of letting subagents read them from disk).
Restructures Phase 5 as five explicit numbered steps. Step 4 mandates
writing each task to $RUN_DIR/task-<N>.md and verifying with test -f;
step 5 requires dropping inline copies once the file is the source of
truth. The phase is "not done" until every task file exists on disk.
Adds a row to Dispatch Hygiene's Pre-Dispatch Validation table that
requires test -f verification of any artifact path the dispatch
references; missing files route back to the producing phase.
Harald Hoyer
236b4d2470