Loading content
Observable symptom: Single point of coordination, single point of failure, single point of privacy exposure. Suitable correction: A thin hub with strong specialists. Keep the orchestrator's prompt and tools small; push work into specialists.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
God Orchestrator names the anti-pattern where one agent absorbs too much coordination, decision power, and data access. It makes multi-agent systems look simple, but brittle.
The anti-pattern emerged from practice in multi-agent systems, where a single orchestrator bundles planning, routing, tool access, and often context state. That concentrates coordination, failure, and data exposure in one place while increasing latency, debugging effort, and security risk. The label warns against loading too much responsibility into one central agent and confusing control with actually doing the work.
Think of a control room that sees every request first, makes every decision, and manages every handoff. That feels orderly, but it becomes a choke point once the same node is also expected to do specialist work. The sturdier model is a thin hub: it accepts input, decides only what is needed, dispatches to specialists, and keeps its permissions and context small.
All important decisions pass through one instance and slow the system down.
If the central node fails, the whole setup loses its control point.
A narrow access radius reduces which data and tools the orchestrator can touch.
Domain work is delegated to agents or tools with a clear role.
Work moves through explicit steps instead of being accumulated in one node.
A thin control node directs work without taking over the specialist tasks itself.
The term is useful when designing agentic workflows, especially where privacy, cost, latency, or fault tolerance matter. A central orchestrator can simplify prototypes and improve observability, but it scales worse and widens the attack surface. For small, tightly bounded flows, a central node may still be enough; the problem starts when it becomes the place where everything must pass.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.