chapter three
3 Multi-agent pipelines and orchestration
This chapter covers
- Why single-agent designs break down in real offensive security workflows
- Composing multiple small agents into staged, defensible pipelines
- Using artifacts as explicit interfaces between agents
- Controlling execution order and failure handling through orchestration
- Enforcing authorization and scope with safety gates and human review
- Managing shared state and memory without embedding hidden reasoning
- Designing multi-agent systems that fail visibly and recover cleanly
In the previous chapter, we established the definition of an AI agent: a decision-making entity that reasons, acts through tools, and records its behavior as artifacts. We created a triage agent operating within a clearly defined scope. However, real offensive security workflows rarely stop at a single decision point. Reconnaissance feeds triage. Triage feeds prioritization. Prioritization feeds testing, reporting, or escalation. Each stage produces artifacts that shape what happens next. Attempting to collapse this process into a single “smart” agent results in brittle systems, opaque behavior, and failures that are difficult to diagnose or defend against.