Spec / 004-06 · pattern 06 of 06
Orchestrator
Orchestrators are supervisors. They assign, validate, and halt. They should not impersonate every worker.
Goal → orchestrator → worker → result (orchestrator still owns stop)
Station 01 of 04 · Goal
- intake
- lead
- agent
- output
- packet on the wire
intake
Goal
The job.
Goal.
Shape
The type is the contract. If you cannot write it, you do not have this pattern yet.
type Orchestrator = {
assign: (goal: string) => Task;
validate: (artifact: unknown) => boolean;
stop: (reason: string) => void;
};When to use it
Use when several specialists must share state and a stop policy.
Not this
Not a specialist that also happens to talk the most. If the coordinator does the work, you are back to a single agent.
Risks
- 01
The orchestrator does all the work.
- 02
No validation on handoff.
Agents that use this pattern
102 agents · page 1 of 5
Showing 1–24 of 102
Read next
Multi-Agent Systems
Multi-Agent Systems: Supervisors, Subagents, Parallel, A2A
Multi-agent systems are workflows with roles, handoffs, and shared state — not extra names on the same chat.
Agentic Workflows
Agentic Workflows: Branch, Chain, Merge, Suspend, Stream
Reliable multi-step systems are graphs with conditions, not a single while-loop that hopes.