Multi-Agent Loop Failures Are Org-Design Failures, Not Prompt Failures

Most multi-agent setups eventually hit the same wall: agents bouncing between each other, reviewers asking for one more polish pass forever, research workers spawning indefinite subtopics, tool calls spiraling until the recursion limit kicks in. Framework docs call these “loops” and offer a max-iteration knob. One hypothesis gaining traction is that the knob treats a symptom, and the real issue is how agents are organized.

The pattern that keeps reappearing: when agents are designed as peers (researcher talks to analyst, analyst talks to writer, writer hands back to reviewer), nobody clearly owns the outcome. Every agent can keep asking another agent for more work. The graph has stop conditions on paper, but no single agent has the authority to declare “this is done, stop the run.” That authority is implicit and gets diluted across the peer network.

The fix is to treat the agent network as an org chart with explicit reporting lines, not a chat room of peers. Proposed layers:

• Chair (top-level authority, can terminate)
• Strategy Office
• Division Manager
• Team Lead
• Specialist Worker
• QA and Policy as separate staff offices that can reject and escalate but cannot spawn unbounded new work

Key mechanics:

• One accountable mission owner per run
• One owner per workstream
• Finite delegation depth
• Typed return contract per worker: status, evidence, output, blockers, next action
• Manager-only authority to reopen or terminate
• Memory lives at the authority layers; specialists get scoped context only

The reviewer-recursion failure mode in particular gets killed when verifiers are structurally allowed one reject pass, then must escalate.

Existing frameworks already have the primitives:

• CrewAI — hierarchical process where a manager validates worker output
• LangGraph — supervisors, subagents, and explicit recursion limit
• OpenAI Agents SDK — manager-style orchestration distinct from peer handoffs
• AutoGen — GroupChatManager
• Anthropic — orchestrator-worker research system

The underused idea: treat the manager not as a moderator for an open group chat but as a formal reporting line with authority to terminate.

Two open concerns:

1. Hierarchy can become its own bottleneck — if every decision routes upward, the chair becomes a single point of latency and failure.
2. Escalation-as-feature only works if the top has real stop authority. If the chair just calls another LLM that calls more LLMs, the loop just moved one floor up.

Repo with the proposed org chart layers: github.com/jeongmk522-netizen/agentlas_org_chart