Architecture
A sequential pipeline multi-agent architecture where agents are arranged in a strict sequence. Each agent transforms or enriches the output of the previous one, then passes it forward. No central orchestrator — the flow is deterministic like an assembly line.
research_agent {# Research Agent
n1: rectangle label="Summarize Sources (RAG)"
n1.handle(right) -> outline_agent.n2.handle(left) [label="Raw Sources"]
}
outline_agent {# Outline Agent
n2: rectangle label="Structure Headings"
n2.handle(right) -> writer_agent.n3.handle(left) [label="Document Outline"]
}
writer_agent {# Writer Agent
n3: rectangle label="Draft Full Text"
n3.handle(right) -> editor_agent.n4.handle(left) [label="First Draft"]
}
editor_agent {# Editor Agent
n4: rectangle label="Refine Tone & Grammar"
n4.handle(right) -> seo_agent.n5.handle(left) [label="Refined Text"]
}
seo_agent {# SEO Agent
n5: rectangle label="Add Keywords & Meta"
}
Architecture
A supervisor-worker multi-agent architecture where an orchestrator agent receives a high-level goal, breaks it into subtasks, delegates each to specialist worker agents (researcher, writer, QA), monitors execution, handles failures, and synthesizes results. The orchestrator manages but does not execute tasks itself.
Architecture
A swarm multi-agent architecture where multiple agents work on the same or related tasks simultaneously, with no central coordinator. Their outputs are then aggregated, voted on, or merged by a dedicated aggregator node. Agents may compete — the best output wins.
Architecture
A hierarchical multi-agent architecture with multi-level organizational structure. A top-level executive agent manages mid-level team lead agents, who each manage their own pool of specialist workers. Teams within teams — the hierarchy maps to domain separation.
Architecture
The most architecturally sophisticated multi-agent pattern. Agents are assigned not just roles but opposing incentives. A Planner is optimistic about goal completion. A Critic is constitutionally skeptical and holds veto authority. Errors get caught through adversarial pressure rather than trusting a single model's self-assessment.
Architecture
An assembly-line architecture where agents are arranged in a strict sequence. Each agent transforms or enriches the output of the previous one, then passes it forward. Best for tasks with clear sequential dependencies — document processing, content production pipelines, compliance workflows.
Architecture
A sequential pipeline architecture chaining multiple agents in a fixed order (parse → enrich → analyze → format), which is a common 'LLM microservices' setup when each step can be isolated. This structure is often used in document processing and ETL-like workflows because each step is testable and predictable.