The Orchestration Pattern Selector

Choose an orchestration pattern for this multi-agent system.

Sub-tasks: [LIST]
Dependencies between them: [DESCRIBE]
Shared state needed: [DESCRIBE]
Failure tolerance: [WHAT HAPPENS IF ONE FAILS]

Evaluate these patterns against my requirements:
1. PIPELINE — output of one feeds the next, no barrier
2. FAN-OUT / FAN-IN — parallel workers, results collected
3. COORDINATOR — one agent delegates and synthesises
4. PEER — agents communicate directly
5. HIERARCHICAL — coordinators of coordinators

For each: does it fit, what does it cost, what breaks.

Then recommend one, and produce:
6. The control flow, step by step
7. What my code controls vs what an agent decides
8. Where barriers are genuinely needed vs where they add latency
   for no benefit
9. Failure handling: what happens when one branch fails
10. How results are combined
11. The simpler version of this that would deliver 80% of the value

Barriers are the most common inefficiency. Flag every place I have
one that is not genuinely required.