Spec / 004 · patterns

Architectures

Architecture is how model, tools, memory, and control flow are arranged. Pick the smallest pattern that keeps the job inspectable. These are maps, not live model runs.

patterns

stations on the maps

1006

catalog agents

01
Input → agent → tools → output
Single Agent
One agent, a model, and a small tool set complete the task.
4 stations · 199 catalog agents
When to use
Use when one role and a few tools can finish the task without specialist handoffs.
Open pattern →
02
Input → plan → tool → check → output
Tool Agent
The model cannot finish without observations from tools.
5 stations · 505 catalog agents
When to use
Use when the task depends on search, files, browsers, or APIs.
Open pattern →
03
Goal → plan → act → result
Planning Agent
The plan is an artifact produced before or between actions.
4 stations · 152 catalog agents
When to use
Use when the task has dependencies, multiple tools, or a need to stop early.
Open pattern →

How they differ

Split only when artifacts are real. Add memory only when notes must survive a session. Add an orchestrator only when someone must stop the run.

Pattern	Split?	Extra store?	Supervisor?
Single Agent	No	No	No
Tool Agent	No	No	No
Planning Agent	No	No	No
Memory Agent	No	Yes	No
Multi-Agent System	Yes	No	No
Orchestrator	Yes	No	Yes

Read Agent Architecture · assemble a shape on /builder.