technical-term · Multi-agent & protocols · emerging · Reviewed
Orchestrator or supervisor agent
A coordinating component that decomposes work, routes tasks, monitors progress, and resolves or escalates outcomes across agents or tools.
Definition
An orchestrator can be deterministic software, a model-driven supervisor, or a hybrid. It assigns bounded work, carries shared state, applies budgets, gathers results, and decides whether to continue, retry, combine, block, or escalate. Coordination does not make the orchestrator an independent verifier or governance authority.
Supervisor patterns are common in frameworks, but reliability and governance vary widely.
Why it matters
A deterministic orchestrator is preferable when routing rules are known.
A model-driven supervisor helps when decomposition is uncertain but must operate inside explicit authority and termination bounds.
System anatomy
- Decomposition
- Turning a goal into bounded tasks.
- Routing
- Selecting the appropriate agent, tool, or human.
- State
- Tracking progress, dependencies, budgets, and evidence.
- Resolution
- Combining results and handling disagreement or blockage.
Important distinctions
- Governance
- An orchestrator coordinates execution; governance establishes rules, standing, and accountable decision rights.
- Verifier
- A supervisor that commissioned work is not automatically independent from the work it evaluates.
Implementation signals
- Keep orchestration policy explicit and inspectable
- Prevent recursive delegation beyond budgets
- Route unresolved disagreement to a named human
Failure modes
- Supervisor becomes a single unbounded authority
- Task results are merged without evidence or conflict checks
Sources and further study
- Anthropic — Building effective agents
A foundational distinction between fixed, code-orchestrated workflows and systems in which a model dynamically directs its process and tool use.
Use in this library: Primary definition. The workflow-versus-agent distinction is a useful architecture boundary, not a universal taxonomy or proof that autonomous execution is preferable.
engineering · engineering · Published 2024-12-19 - OpenAI — An open-source spec for Codex orchestration: Symphony
An orchestration specification that connects project work, isolated agent execution, and reviewable delivery state.
Use in this library: First-party case study. This first-party account documents one organization, product, or implementation context and should not be generalized without local evidence.
engineering · engineering · Published 2026-04-27 - DeepLearning.AI — Agentic AI
A practitioner course organizing agentic systems around reflection, tool use, planning, multi-agent workflows, evaluation, and optimization.
Use in this library: Official guidance. Course taxonomy is instructional rather than normative; it does not itself define enterprise authorization or assurance requirements.
course · course · Published 2025