Architecture№ 78DBAI · Agent Team Builder
Architecture·April 20, 2026·7 min read
The orchestrator pattern, explained
The orchestrator is not a smarter agent. It is a smaller one with a clearer job: route, sequence, escalate.
An orchestrator's prompt should fit on a postcard. It picks which specialist runs next, hands them the right slice of context, and decides when the work is done.
What it does not do
- Write copy
- Crunch numbers
- Make domain calls
- Talk directly to customers
Resist the urge to load it up with domain knowledge. The moment the orchestrator starts answering questions itself, the team collapses back into a solo-agent shape and the benefits evaporate.
A useful test
If you removed every specialist and only ran the orchestrator, the output should be empty or trivial. If it still produces real work, you have built a hero, not a router.