// Orchestration · ~2 min read
Supervisor
Reach for it when: workers need a referee that picks who goes next and can reject their output.
After this lesson you can: Put a referee in front of workers that picks who goes next and can reject unsafe output.
// 60-second mental model
How to hold it in your head
Workers propose; a supervisor decides who runs next and what is allowed to leave. The supervisor does not write the reply — it routes, scores, and vetoes.
In LangGraph, a supervisor is a central agent that decides which worker runs next. This lesson teaches a stricter referee version: the supervisor also scores each result and can veto it — accept, reject, or hand it to another worker — when it is unsafe or breaks the agreed rules. It never drafts.
How this differs
Both an orchestrator and a supervisor coordinate workers. In this course neither drafts the content itself (in many frameworks they also write the final reply). An orchestrator breaks the goal into parts and merges the results. A supervisor picks the next worker and can reject what comes back.
// Mini architecture
Workers propose · supervisor routes and vetoes
The user goal goes to a Supervisor that checks and scores work. The Supervisor routes or reassigns a task to Worker A or B, and the worker proposes a result back. If the Supervisor vetoes it, the task is reassigned or refused; if not, it becomes the final answer.
The supervisor’s only writes are route, score, and veto — never the worker’s draft.
// Mini-project
Support triage with a veto gate (stub)
Supervisor + two stub workers
Goal: Route a ticket to billing or product stubs; supervisor rejects any reply that invents a refund amount.
- Accept a canned support ticket.
- Supervisor picks `worker_billing` or `worker_product` from keywords.
- Worker stubs return a draft reply (one includes a fake refund number).
- Supervisor scores against a contract: no dollar amounts unless tool-backed.
- On veto, reassign once or emit a safe refusal.
- Log route → result → accept/veto for the demo.
Stubs are enough. The lesson is the referee contract — route and veto, do not draft.
// Common failure
What goes wrong
Symptom
Supervisor writes the answer itself — workers become decorative.
Fix
Restrict the supervisor to route/score/veto tools only. Ban free-text “I’ll handle it.”
// Self-reflection
Sit with this
Where do you need a referee more than another specialist?
Sources
Session only. Nothing is saved.