v1 · architecture
Orchestrated
coordinator + research / write / edit
Orchestrated architecture
v1 orchestratedA central coordinator analyzes your request, plans a workflow, and delegates to specialists one at a time — researcher, writer, then editor — synthesizing their results into a final answer. Best for content tasks with a clear linear pipeline.
Coordinator
Researcher
Writer
Editor
delegated one at a time · results synthesized by the coordinator
How it works
- 1A coordinator analyzes the request and plans an ordered workflow.
- 2It delegates to one specialist at a time (researcher → writer → editor), passing context forward.
- 3Each specialist does its work and returns to the coordinator.
- 4The coordinator synthesizes the results into a final answer.
When to use
Linear content pipelines where the steps and their order are clear up front.
Trade-off
A single coordinator is a bottleneck and a single point of failure; no parallelism.
Agents
CoordinatorPlans the workflow and delegates to specialists
ResearcherGathers facts, sources, and information
WriterDrafts and structures the content
EditorPolishes clarity, grammar, and tone
Note
The workhorse pattern. A strong coordinator + cheap specialists is reliable and easy to debug — but the coordinator is a bottleneck, so keep its turns short and its delegation explicit.