A multi-agent org that doesn't know when it's done will run forever — agents handing work back and forth, burning tokens, converging on nothing. Every orchestration needs an explicit termination condition: the specific signal that says "the goal is met, stop." Without it, the only thing that ends the run is your budget.
Two guardrails do the work. A clear done-condition ("stop when the brief has an answer, three sources, and a next action") tells the org what success looks like. A hard ceiling (max turns, max cost, or a human checkpoint) catches the case where it never reaches success and would otherwise loop. The best orchestrations have both — a definition of done and a circuit breaker — the same discipline a single build agent uses, scaled to a team.
Run the seed: for a multi-agent task, write its done-condition and its circuit breaker — the specific state that means "finished" and the hard limit that stops a runaway.