Academy

Series · Builders · Steps 3–4

Agent Architecture & Coordination

How do you build an AI agent you can actually trust — and what changes when one agent is no longer enough? This series works through the principles of agent architecture and then into coordination: why a precise separation of responsibilities matters, how a specialist differs from a simple task executor, and how a set of agents divides labour under the Coordinator–Worker–Delegator pattern without losing messages or collapsing. The principles are general; the aim is to introduce patterns that hold whatever software framework you use.

12 pieces, in order

  1. Part 1: How an AI agent thinks

    Step 3 · 5 min
  2. Part 2: One agent or many? When each one fits

    Step 3 · 7 min
  3. Part 3: Three lessons the human mind offers agent architecture

    Step 3 · 5 min
  4. Part 4: From worker to specialist: an agent that owns a domain

    Step 3 · 4 min
  5. Part 5: The Coordinator, the Worker, and the Delegator

    Step 4 · 8 min
  6. Part 6: Event-driven by design: agent teams that don't lose messages

    Step 4 · 6 min
  7. Part 7: Tracing a request through a multi-agent system

    Step 4 · 5 min
  8. Part 8: Save first, then publish: a simple rule for not losing work

    Step 4 · 5 min
  9. Part 9: Cognitive Least Privilege: your agent should know only what it needs

    Step 4 · 4 min
  10. Part 10: Defending against prompt injection and jailbreaks — and reducing hallucination

    Step 4 · 7 min
  11. Part 11: You might not need an agent

    Step 3 · 8 min
  12. Part 12: How agent teams coordinate: a guide to choosing the right shape

    Step 4 · 10 min

All series