# Coordinator Directives Written **only** by the coordinator (the human's planning session). Agents: read the latest round at session start and after every milestone via `git fetch origin && git show origin/main:plan/DIRECTIVES.md`. The newest round addressed to your lane overrides older rounds and, where in conflict, your lane brief. Never edit this file. --- ## Round 0 — 2026-07-16 — Run order & protocol **Execution order:** 1. **Now: `foundation` only.** Nothing else starts until foundation merges to `main`. Foundation agent: contracts correctness beats speed — lanes will hard-depend on your API shapes, schema, pose math, and synthetic fixtures. 2. **After foundation merges — start lanes in this priority order** (all four concurrently if capacity allows; if running fewer sessions, start in this order): 1. **Lane C (viewer)** — longest lane and the earliest validation of the API contract; starts first. 2. **Lane A (media)** — the core real-footage capability; small surface, should finish early. 3. **Lane D (events)** — small and fully independent. 4. **Lane B (recon)** — heaviest external dependency (COLMAP) and the most graceful-degradation slack; safe to start last. 3. **Merge policy:** merge to `main` as soon as your lane's acceptance passes — do not wait for other lanes. Expected finish order: A, D, then C, then B. 4. **After all four merge: `integration`.** **Standing protocol (all agents):** - Maintain `plan/status/.md` per `plan/status/TEMPLATE.md` — session start, every milestone, every blocker, before merge. Push status commits to your branch immediately; the coordinator reviews between rounds by reading these files. - If blocked > 30 minutes on an ambiguity, write the blocker to your status file, push, and move to another task in your lane rather than guessing on a frozen contract. - Evidence discipline: a checked acceptance box must name the test or the exact command + output that proves it. *(Future rounds will be appended above this line as the coordinator reviews status files.)*