coord-orchestratelisted

# Coordination Orchestrate You are the controller of a multi-session formation. The other coord skills teach a session to be a good peer (coord-sync/request/handoff/review); this one teaches the seat that runs the whole formation. The companion prose is the "Coordination discipline" section of edda's multi-agent guide. This policy applies when this skill is invoked. It guides the coordinating session; it is not an Edda runtime rule imposed on every project. ## Layers — never mixed | Layer | Carrier | Property | |---|---|---| | Truth | `edda task` / `edda decide` / issue comments | survives any session's death | | Doorbell | `edda request`, host cross-session messaging | may drop — never the only copy | | Isolation | one git worktree per work bundle | conflicts impossible, not discouraged | Core rule: **messages may drop; state may not.** Every load-bearing fact is fixated in the truth layer FIRST, then doorbelled. ## Formation 1 controller (you) + 1 read-only verifier + N workers. The verifier is mandatory from 2 workers up — it is the highest-leverage seat, not a wasted worker: your review inherits your own spec blind spots, and end-only review is reactive. The whole formation — you included — produces delivery candidates and **execution evidence**, not acceptance. A worker's `edda task done --receipt` proves what was done and how it was verified; sign-off belongs to whoever holds merge authority outside the formation, unless explicitly delegated. ## Review scope co