Part 7 of 12 · 1 min read
Choosing a shape
- Fixed process, known steps: a workflow (sequential, conditional or parallel). Lowest cost and highest predictability.
- One clear domain per request: route to a specialist.
- Requests that must be decomposed at run time: orchestrator-workers; give the orchestrator the best model and typed results (module 8 of Level 7).
- Specialists that know best when a request is not theirs: handoff with a hop limit.
- A check that is cheaper than the error: add a critic, and measure its detection and false-rejection rates first.
- Exploration with no fixed path: conversation-driven shapes; budget them by message count.
- Compose: a node can be a sub-system, so use a workflow inside an orchestrator, or a critic inside a worker.