Consent Decision Rule¶

Decision rule — instantiates Consensus Convergence

Adopts a proposal the moment no participant holds a reasoned, paramount objection — closure by absence of blocking dissent rather than by counting support.

A Consent Decision Rule flips the question a group asks itself at the point of decision. Instead of "how many are in favor?" it asks "does anyone have a reasoned objection strong enough to block?" — and if none does, the proposal is adopted. Its distinctive move is making dissent the operative variable: closure is defined by the absence of a paramount objection, not by the presence of enthusiastic support, so a proposal that everyone finds merely "good enough for now and safe enough to try" passes without anyone having to pretend to love it. This is the sociocratic sense of consent, and it is deliberately weaker than consensus (all-agree) and different in kind from a majority vote (most-agree).^[1]

Example¶

A twelve-person worker cooperative that runs a bakery needs to decide whether to close on Mondays. Under a majority vote this would split the room and leave a sore minority. Under a consent rule, the facilitator states the proposal, answers clarifying questions, and then goes around asking only one thing: do you have a paramount objection — a concrete reason this would harm the co-op's ability to do its work?

Two members dislike the idea but have no such objection; their preference is noted, not treated as a block. One member raises a real one: the Monday close would break a standing wholesale contract. That objection is paramount, so the proposal doesn't pass as written — instead it is amended to "closed Mondays once the wholesale contract is renegotiated." On the next round no paramount objection remains, and the amended proposal is adopted. Nobody counted votes; the decision converged by resolving the one objection that actually mattered.

How it works¶

The rule's leverage comes from the distinctions it enforces at the moment of closure:

Objection, not preference, is the gate. Disliking a proposal is not a block; a block requires a reasoned objection tied to the group's aim and within scope. This separates "I'd prefer otherwise" from "this will cause harm."
A valid objection routes to amendment, not defeat. A paramount objection doesn't kill the proposal; it becomes the next thing to resolve, so the objector's information is folded in rather than outvoted.
Silence-of-objection is explicit closure. The decision is declared adopted when the round produces no remaining paramount objection — a positive, on-the-record stopping point, not a vibe.

Tuning parameters¶

Objection bar — how strong an objection must be to count as paramount (any concern versus demonstrable harm to the aim). A low bar approaches unanimity and stalls; a high bar approaches majority rule and loses the point.
Scope of a valid block — what an objection is allowed to be about (this decision's domain only, versus anything). Tight scope keeps closure reachable; loose scope lets one person hold everything hostage.
Rounds before fallback — how many amend-and-recheck cycles before the decision escalates or defaults. Fewer rounds decide faster; more rounds extract more information.
Who may block — everyone present, or only those the decision binds. Restricting the block to affected parties keeps it honest.

When it helps, and when it misleads¶

Consent shines where a group must keep deciding together over time and can't afford a permanent winning-and-losing faction — it lowers the cost of "yes," surfaces the objections that carry real information, and converts them into amendments instead of grievances. Its failure mode is objection inflation: without a disciplined bar for what counts as paramount, mere preferences masquerade as blocks and the rule collapses back into stall-prone unanimity. The mirror failure is a facilitator who, wanting to close, waves off a genuine objection as "just a preference." It is also misused to pressure a lone holdout — "you're not really blocking, are you?" — turning a legitimacy device into a conformity engine. The discipline is a written, agreed definition of a paramount objection and a facilitator willing to hold the proposal open until a real one is resolved.

How it implements the components¶

Consent is a closure rule built around dissent, so it fills exactly those two:

dissent_handling — it is the archetype's dissent channel in its most load-bearing form: a reasoned objection legitimately halts closure and reshapes the proposal.
closure_rule — "adopted when no paramount objection remains" is a distinct, explicit closure condition, qualitatively different from a vote's tally threshold.

It does not tally support (convergence_target as a count — that's Consensus Vote), build the proposal being tested (synthesis_frame — Consensus Workshop), or preserve the reasoning of dissent that was overridden into the permanent record (minority_report — Minority Statement Protocol).

Instantiates: Consensus Convergence — consent is one of the archetype's closure conditions.
Sibling mechanisms: Consensus Vote · Minority Statement Protocol · Consensus Workshop · Delphi Process · Disagreement Register · Evidence Briefing Packet · Facilitated Decision Meeting · Scientific Consensus Process · Stakeholder Alignment Session · Standards Committee Process

Notes¶

Consent and voting answer different questions and often sit in the same process: consent to whether the group can live with a proposal, a vote to choose among proposals when several survive that test. Confusing the two — running a consent round as if it were an approval poll — is how a paramount objection gets quietly outvoted.