orchestrationlisted

# Orchestration One task. Five stages. Each stage produces an artefact the next stage consumes. **No artefact, no advance** — that is the whole mechanism. You are the orchestrator. Agents cannot call each other; they have no Agent tool. Every hand-off passes through you, which is what makes the chain inspectable. ## The pipeline ``` USER GOAL │ ① DISCOVER product-manager, business-analyst │ → problem, affected segment, success metric, non-goals │ ⛔ GATE: no measurable success metric → stop and ask the user │ ② DESIGN the relevant architects │ → options, trade-offs, failure modes, ADR │ ⛔ GATE: no ADR for an irreversible decision → do not build │ ③ BUILD engineers from the owning team │ → implementation, tests, migrations, instrumentation │ ⛔ GATE: no tests on the failure path → not done │ ④ VERIFY code-reviewer + the quality agent for the changed area │ → ranked findings, each with a concrete failure scenario │ ⛔ GATE: any unresolved high-severity finding → back to ③ │ ⑤ RELEASE production-readiness-engineer, release-manager, SRE → full test run, version decision, CHANGELOG entry, release notes, rollout plan, rollback, abort criteria ⛔ GATE: red test, or no owner / runbook / rollback → no ship ↓ RELEASE PACKA