⌕ Begin

Doctrine · Doctrine · Aug 2026 · 5 min

How do you scale AI agents?

From one agent to a fleet — what actually has to grow, in what order.

The short answer

Scale the gate before the fleet. Generation is cheap; judgment is scarce. The review-and-merge discipline has to grow before the agent count does, or volume just becomes debt. Then scale context — shared durable memory is the real scaling law. Then scale hands — machines, not browser tabs. And spend model strength where judgment lives, not everywhere.

The order of operations

First, the gate. One agent's output can ride on your attention. Ten agents' output cannot. Before adding the tenth agent, the vet-and-merge lane from the fleet doctrine has to be real: one orchestrator that checks everything, a human who leads every merge, no lane that lands itself. Teams that skip this don't get ten times the progress — they get unreviewed output at machine speed, which is a polite name for debt.

Second, the memory. The scaling law nobody prices in: agent #40 must start as informed as agent #1 ended. Decisions, doctrine, past mistakes, standing preferences — held in durable shared memory, not in one person's chat history. Without it, every new lane pays the full cost of rediscovery, and your fleet's learning curve resets daily. With it, context compounds instead of evaporating.

Third, the machines. Hands scale by adding claimed machines, not by exhausting one laptop — the pattern in running agents on remote machines. When execution lives on a fleet of visible, governed boxes, adding capacity is an infrastructure decision instead of a heroic one.

Fourth, the spend. Not every lane needs the strongest model. Mechanical transforms, sweeps, and formatting ride cheaper models; judgment calls, architecture, and review get the strong ones. Matching model to task is the difference between a fleet you can afford to run daily and a demo you run twice.

What breaks it

Adding agents before the gate exists. Scaling to impress rather than to ship. Fleet-wide amnesia because memory was "phase two." Model maximalism that makes every lane cost like the hardest one. And the quiet one: nobody owning the orchestration, so twenty agents each answer to a different vibe. Scale is a governance achievement wearing a technology costume.

Ten agents with a gate ship ten agents' work. Ten agents without one ship a mess with excellent throughput.

This page extends the fleet doctrine to the question of growth. For the layer underneath all of it, see what AI agent infrastructure is.