The fleet can build anything and remembers nothing. Someone has to carry what the machines cannot.

Watch a good Fleet Lead work for an hour. Six agents in flight at once. Two are drafting against different halves of the spec, one is writing harness checks from the criteria, one is grinding through a migration, and two are parked, waiting on a judgment call their operator will make between other judgment calls. Work merges, checks run, something lands. A refactor that would have been a two-week argument goes in quietly before lunch. It looks less like programming than like conducting, and the throughput coming off one desk is, frankly, a little absurd. The six is a soft count, too. Agents spawn agents when the work splits, the pattern production orchestrator systems already run [1], and the formation swells and thins by the hour. In the work we run, the spikes reach scores of agents under one orchestrator when the day calls for it.