AGENTS AT WORK · 03 A visual series

Orchestrator & specialists

One hub, four specialists. The hub dispatches a packet to each and collects the result — it never does the specialist's work itself. Turn a specialist off and see what happens.

ORCHESTRATOR delegates, never builds REQUIREMENTSSPECIALIST SCHEMA SPECIALISTSPECIALIST API DESIGNSPECIALIST REVIEW SPECIALIST

The problem this replaces

One agent, every job

ONE AGENT, EVERY JOB requirements schema design API design diagrams non-functional reqs review docs gap analysis standards check publish

Everything lives in one head. When one job goes wrong, there's nowhere smaller to point at.

How it works

Every spoke is the same round trip

ORCHESTRATOR packet out result back SPECIALIST
Same round trip for every spoke — only the packet's name changes. The specialist does the work; the hub only carries the packet.

If a specialist can't run, the orchestrator reports the missing packet — it does not write a fake schema or a fake review to fill the gap.

See it in action

One design, four round trips

"design: add customer export" → requirements: filters, CSV, admin-only → schema: export_job table → API: POST /exports → review: approved

Four specialists, four packets back — the orchestrator assembles the final design doc from what it received.

So what

When review misbehaves, you fix the review specialist — not the whole thing.