# Decision-Venue Legitimacy Determines Whether Agreement Binds ## Claim In open-source governance, whether a group's agreement counts as a project decision depends on whether the right quorum — authors, release squad, core committers — was actually present, not on the fact that agreement was reached. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds where a project has role-based decision rights (maintainers, release leads, component owners) that a merge proposal or RFC process routes through formally. - Breaks down in flat, consensus-only communities that have no defined venue distinction — there, "agreement was reached" and "a decision was made" collapse into the same event. - Does not evaluate whether the agreement reached in the informal venue was substantively correct — only whether it was procedurally binding. ## Evidence WordPress 7.1's abilities-expansion proposal drew a governance objection distinct from the technical pushback: a contributor-call consensus to expand abilities was cited as settled, but the objection was that neither the feature's own working group, the release squad, nor broader core committers were in that room. The merge proposal — not the call — is what the project's process treats as the actual decision point. ## Links - [[3. Resources/Permanent Notes/Core Abilities Must Be Consumer-Neutral Primitives Not One Interface's Mirror]] — applies-in: same source dispute, the companion design-shape objection to this note's process objection — together they show a proposal can fail on shape and on venue independently. - [[3. Resources/MOCs/Open Source Governance MOC]] — evidence-for: a recurring governance-legitimacy question this MOC tracks across projects. - [[3. Resources/Permanent Notes/Absence From an Open Venue Is a Choice Not an Exclusion]] — contrasts; that note diagnoses why a group never showed up to a venue at all, this one diagnoses whether an agreement reached inside the venue actually binds. Read together: absence and non-binding agreement are two different ways a venue can fail to produce a real decision. ## Tests / falsifiers - Find a WordPress core decision that was made in an informal venue (a Slack thread, a contributor call) and later stood without being re-ratified through a merge proposal — this would weaken the claim that venue determines bindingness. - Check whether the 7.1 abilities proposal was ultimately re-decided through the formal merge-proposal process, or whether the informal consensus was allowed to stand — the outcome tests whether the objection actually changed anything. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Readwise/Articles/Proposal to Expand Abilities in WordPress 7.1 Draws Pushback From Component Maintainer Over Testing and Readiness]] — The Repository on the WordPress 7.1 Abilities API dispute.