V2 dispatches sub-agents across four milestones (M1–M4) with multiple artifacts per milestone. Within each parent's children, two dispatch patterns are possible: parallel (all N fan out, fast wall-clock, minimal cross-sibling coherence) or sequential (one at a time, slower, tighter coherence as each reads prior's committed output).
V1 #158's 'per-unit dispatch' chose sequential for M3 specifically. The earlier draft of this redesign recommended parallel everywhere on uniformity grounds. The operator pushed back during the 2026-05-27 grilling:
'M1 (Strategy) is the foundation of all other curriculum (equivalent to the PRD or spec-kit for apps), so i would lean towards methods that produce higher quality content... For M2, while the user is reviewing Unit 1, unit 2 can be generating, decreasing token burn if the direction of units is wrong or if specific units need clarification.'
Within-parent siblings dispatch sequentially. Next sibling's sub-agent fires when prior sibling reaches APPROVED state (teacher endorsed but not yet finalized). Cross-parent siblings parallelize.
| Threshold | Overlap | Token-burn risk | Verdict |
|---|---|---|---|
| (α) DRAFT | Maximum | High — teacher may reject | Too aggressive for foundation |
| (β) APPROVED | Significant | Low — teacher endorsed | Balanced — chosen |
| (γ) FINALIZED | None — defeats overlap | Zero | Defeats purpose |
Parent finalized → sibling-1 dispatched → commit (draft) → teacher reviews → approves → sibling-2 dispatched (while teacher still on sibling-1) → ... → all siblings finalized → parent gate close → next milestone or next parent.