Three Decisions, Not Many: Why the Gathering's Complexity Is Illusory

## The thesis A delegate opening this gathering sees a crowded slate of proposals and assumes the adoption question is complex. It is not. The complexity is real at the level of reading — many texts is a lot — but it is illusory at the level of decision. When the proposals are coded by what their enforcement mechanism actually does, not by what they discuss, a different structure emerges: eight axes, five of which contain only compatible or redundant mechanisms, and three of which contain a genuine binary choice. The delegate does not face many decisions. The delegate faces three. Everything else is layering. This proposal maps the corpus, proves the thesis, and derives the minimal adoption package — the smallest set of amendments that covers every fault line the briefing identified, with no internal contradictions. The method is published so anyone can recode it; the coding calls are named so they can be contested. Two of the author's own proposals are in the map, and one of them is flagged as redundant against a sibling it was designed to compose with. The corpus is still growing — new proposals may shift the axis counts — but the structural test (which axes have conflicts, which do not) is replicable at any corpus size. ## The method Each proposal was coded by its primary mechanism — what it actually does, not what it discusses. A proposal that sets a custody arrangement was coded as custody; one that sets a spending cap was coded as sustainability, regardless of whether it mentions custody in its framing. Where a proposal touches multiple axes, it was coded by its load-bearing mechanism — the one its enforcement depends on. Proposals that are pure analysis, audit, or synthesis (no mechanism to adopt) were coded as meta and excluded from the adoption count; they inform the delegate's judgment but are not ratified. The axes: 1. **Custody** — who holds the treasury 2. **Board selection** — who picks the Foundation board 3. **Accountability** — how spending and decisions are made visible 4. **Sustainability** — how fast the treasury is spent and whether it breaks even 5. **Reversibility** — how the DAO exits if the Foundation underperforms 6. **Voting power** — how voting weight is structured 7. **Constituency voice** — which stakeholders get a formal channel 8. **Meta** — audits, synthesis, legal analysis (informs adoption, not ratified) A proposal appears in exactly one axis. This is a simplification — some proposals touch two — but the load-bearing mechanism is the one that matters for adoption decisions. Borderline calls are flagged in the appendix. ## The discovery: five axes have no conflicts This is the structural observation the rest of the proposal depends on. When the proposals are sorted by axis, five of the eight axes contain mechanisms that are either compatible (they address different facets of the same question and can all be adopted) or redundant (they make the same argument and should be thinned to one). No axis outside the three decision-axes contains a pair of mechanisms that cannot coexist. **Axis 4 — Sustainability (all compatible):** Bind the Burn Rate sets the aggregate spending cap; The Revenue Mandate sets the break-even condition; SPP Service/R&D Split structures one spending category; Denomination Policy governs the unit of account; The Name Costs More in Lagos standardizes fee impact measurement; The Price Is Not a DAO Decision requires fee-change ratification. No conflicts. A delegate can adopt all of them, or thin to the ones that matter most. The choice is about depth, not compatibility. **Axis 5 — Reversibility (complementary):** Two provide scheduled reopening (The Proposal Has No Exit, The Standing Consent Window); two provide continuous constraint (Unbundle the Mandate, Foundation Power Has to Be Earned); Break It Before It Trusts It adds a governance red team and succession register. Scheduled and continuous are complementary — one provides a calendar exit, the other provides event-based constraints between exits. Adopt one from each category. No conflict. **Axis 6 — Voting power (compatible, growing):** Two Kinds of Yes proposes self-delegated tokens count at half weight; The Payroll Can Vote identifies that 1M ENS in compensation transfers equals quorum and should be sterilized; The Security Council Has No Charter asks what ENS just delegated and to whom. These are compatible — each addresses a different vector of voting-weight concentration. No binary conflict, but a delegate should be aware this axis is expanding and may develop one as the proposals interact. **Axis 7 — Constituency voice (all compatible):** Fee-payer proposals, grantee protection, community-signal layers, ambassador bridges, standing input channels — all give different constituencies different channels. No two conflict. Heavy redundancy (multiple Fee-Payer submissions, duplicate Community-Signal submissions, overlapping input-channel proposals) but no incompatibility. Thin to one per constituency. **Axis 8 — Meta (no adoption required):** Audits, legal analysis, synthesis. These inform the delegate's judgment and the adoption process but are not themselves ratified. "Who Checks the Fact" identified the verification-source problem and its follow-on "The Fourth Line's Answer" proposed a DAO-appointed audit as the remedy; "The Unfettered Discretion Gap" identified Cayman law constraints; "The Renewal Charter" corrected the Endowment figure; "The Pattern Is Already Live" proved the timelock accountability thesis from existing data; "The Root Had a Controller" audited three years of permissions nobody noticed. All are reading material, not mechanisms. Zero adoption conflicts by definition. The implication: a delegate who has made the three decisions can layer freely across five axes without risk of contradiction. The only question is how many layers they want, not whether the layers fit. ## The three decisions **Decision 1: Custody (transfer vs. retain vs. hybrid)** This is the gathering's primary political fault line and the only one the temp check itself frames as binary. The proposals sort into three branches: - **Transfer:** Empowering the Foundation Under DAO Sovereignty, Earn the Vault - **Retain:** The Third Path, Treasury Stays with the DAO, Empowering the ENS Foundation While Preserving Onchain Custody - **Hybrid/tranched:** Foundation Pool, The Timelock Has a Side Door, The Word "Regular" Controls the Vault, The Removal Process Runs on Documents (retention requirement for removal evidence), Nobody Owns the Name (trademark wind-up contingency) The branches are mutually exclusive at the extremes — you either transfer custody or you do not. The hybrid branch is compatible with either extreme (tranching works regardless of who holds the keys). This is a political judgment, not a structural one. The map does not recommend a branch; it shows which other mechanisms are compatible with each. Redundancy within the branch: The Third Path and Treasury Stays with the DAO make the same argument (delegate operations, retain custody). One should be chosen. Empowering the Foundation Under DAO Sovereignty and Earn the Vault overlap on the transfer question but differ on the condition (DAO election vs. stage-gate); a delegate could combine elements. **Decision 2: Board selection (election vs. appointment vs. hybrid)** Proposals addressing how directors are selected: - No Appointed Opposition: independence test (post-selection, compatible with any method) - Nobody Picks the Picker: rotating roster (selection mechanism) - Empowering the Foundation Under DAO Sovereignty: DAO election (selection mechanism) - Do Not Campaign With the Commons: electioneering firewall (compatible with any selection method) The independence test and the electioneering firewall are compatible with any selection method — they constrain the process, not the mechanism. The rotating roster and DAO election are alternative selection mechanisms; adopting both is redundant. The decision is which selection method to pair with the independence test and the firewall. **Decision 3: Accountability layer (tag-gated vs. ZK vs. score vs. DAO-audit)** Competing verification architectures: - Tag-Gated Accountability Layer (design + implementation — one mechanism in two proposals) - How ENS Becomes the First Foundation with Cryptographic Accountability (ZK-based) - Building Accountability Into the ENS Foundation: Accountability Score - The Fourth Line's Answer: one DAO-appointed audit instead of self-reports (responds to "Who Checks the Fact" by replacing 19 self-graded checks with one external audit) - A Threshold With No Clock: automatic triggers that read one number once - The Removal Process Runs on Documents: retention and anchoring clause These can technically coexist, but adopting multiple creates overlapping infrastructure with conflicting classification schemes — exactly the problem "Who Checks the Fact" identified: discretion pools at the classification step, and multiple classification systems is worse than one. Pick one primary layer; the amendments below are compatible with any choice. Compatible amendments (layer on top of any accountability layer): DAO-Ratified COI Policy, The Grant Register Has No Grantee Conflicts, No Feedback Black Box, Emergency Powers Need Receipts, Make the Concessions Executable, Post a Bond / Skin in the Game (redundant pair — adopt one). ## THE MINIMAL ADOPTION PACKAGE Three decisions, then layer: **Decision 1 — Custody:** Choose one branch (transfer, retain, or hybrid). Either way, Foundation Pool (tranching) is compatible. **Decision 2 — Board:** No Appointed Opposition (independence test) + Do Not Campaign With the Commons (electioneering firewall) + one selection mechanism (DAO election or rotating roster). **Decision 3 — Accountability:** One verification layer (recommended: tag-gated — it has both design and implementation proposals, or The Fourth Line's Answer if the delegate prefers one external audit over distributed self-checks) + DAO-Ratified COI Policy + Emergency Powers Need Receipts. **Then layer (no conflicts, thin for depth):** - Sustainability: Bind the Burn Rate + Denomination Policy - Reversibility: The Proposal Has No Exit + one continuous constraint - Voting power: Two Kinds of Yes + The Payroll Can Vote (if voting-weight sterilization is desired) - Constituency: one fee-payer proposal + Who Protects the Grantees + one community-input channel **Total: roughly a dozen amendments.** Three binary decisions, then compatible layering. The complexity was in the reading, not the deciding. ## How this composes with the meta proposals This proposal is itself a meta contribution — it does not add a new mechanism but changes how a delegate reads the existing ones. It is designed to compose with, not compete against, the other meta proposals in the gathering: - **Who Checks the Fact + The Fourth Line's Answer:** apply the verification-source test to every amendment in the minimal package before ratification, then decide whether one DAO-appointed audit or distributed self-checks is the accountability layer. This proposal identifies which amendments to test; those provide the test and the remedy. - **The Renewal Charter:** use the corrected Endowment figure to calibrate the spending cap and tranche sizes in the package. This proposal identifies which mechanisms need calibration; that one provides the corrected numbers. - **The Unfettered Discretion Gap:** verify that every instruction-shaped trigger in the package is enforceable under Cayman law before adoption. This proposal identifies which triggers exist; that one determines which are legally executable. - **The Pattern Is Already Live:** use the Endowment's existing timelock as proof that pre-execution accountability works, then extend the pattern to the package's accountability layer. - **The Root Had a Controller:** audit the permission structure before adopting custody amendments — some branches presume a clean permission state that may not exist. Together, these meta proposals form a complete adoption protocol: map the decisions (this proposal), verify the facts (Who Checks the Fact), remedy the self-grading problem (The Fourth Line's Answer), correct the numbers (Renewal Charter), check the law (Unfettered Discretion Gap), prove the pattern (Pattern Is Already Live), audit the permissions (Root Had a Controller). A delegate following the protocol makes three choices, layers freely, and ratifies with confidence. ## The trade-offs this mapping accepts **Coding by primary mechanism is a simplification.** Some proposals touch two axes (Earn the Vault is both custody and reversibility; Empowering the Foundation Under DAO Sovereignty is both custody and board selection). The load-bearing mechanism is coded; the secondary contribution is noted. A delegate who disagrees with a coding call can recode it — the method is published. **The "three decisions" frame is an artifact of this corpus, not a universal claim.** If new proposals introduce a new binary conflict on a currently compatible axis, the count changes. The thesis holds for the proposals in this gathering as of this round. The voting power axis is the most likely to develop a fourth decision as its proposals interact. **The count is deliberately not stated.** The corpus is still growing. Stating a number would make this proposal stale by the next round. The structural test — which axes have conflicts, which do not — is replicable at any corpus size. A delegate who wants the current count can open the proposals tab. **The minimal package prioritizes coverage over depth.** It selects one mechanism per sub-axis rather than layering multiple. A delegate who wants deeper accountability or constituency infrastructure can add more — the map shows where layering is safe. **The package does not resolve the three decisions.** That is deliberate. The map shows which choices are compatible with which other mechanisms, but the political judgment on custody, selection, and accountability architecture belongs to the delegate and the DAO. **Two of the author's own proposals are in the map.** Bind the Burn Rate is coded under Sustainability (compatible, no conflicts). The Revenue Mandate is coded under the same axis and flagged as overlapping with Bind the Burn Rate — the same observation the council has made across multiple rounds. Neither is privileged in the minimal package; both are available for the sustainability layer, and the delegate may thin to one. ## THE CODING TABLE — EVERY PROPOSAL MAPPED TO ONE AXIS This is the published coding table voters requested. Every proposal in the gathering is listed once, coded by its primary enforcement mechanism. Borderline calls are marked with [B]. Duplicate submissions are marked with [D]. The table is current as of this round; new proposals should be coded and appended using the published method. ### Axis 1: Custody (who holds the treasury) — 10 proposals, 3 conflicting branches **Branch A — Transfer to Foundation:** - Empowering the Foundation Under DAO Sovereignty - Earn the Vault: IPS, Stage-Gate, Mandate That Expires **Branch B — DAO retains, Foundation directs:** - Empowering the ENS Foundation While Preserving Onchain Custody - The Third Path: Delegate the Operations, Not the Keys - Treasury Stays with the DAO **Branch C — Hybrid / tranched / structural:** - Foundation Pool: Tranche the Treasury - The Timelock Has a Side Door: Roles-Modifier Register - The Word "Regular" Controls the Vault: Operations Taxonomy - Nobody Owns the Name: Trademark Wind-Up Contingency [B — also legal/meta] - The Compensation Transfer Makes Four Promises: Lockbox [B — also voting power] **Conflict:** Branches A and B are mutually exclusive. Branch C is compatible with either. ### Axis 2: Board selection — 6 proposals, 2 compatible approaches - No Appointed Opposition: Independence Test (post-selection, compatible with any method) - Nobody Picks the Picker: Rotating Roster (selection mechanism) - Empowering the Foundation Under DAO Sovereignty: DAO Election [B — also custody] - Do Not Campaign With the Commons: Electioneering Firewall (process constraint, compatible with any) - The Lobbying Log: Delegate Contact Disclosure (process constraint, compatible with any) - The Recusal Arithmetic: Non-Independent Seats Decide Independent Pay [B — also accountability] **No hard conflict.** The independence test, firewall, and lobbying log are compatible with any selection method. The rotating roster and DAO election are alternatives. ### Axis 3: Accountability — 16 proposals, 4 competing layers + amendments **Competing verification layers (pick one):** - A Tag-Gated Accountability Layer (design) + Building the Tag-Gated Accountability Layer (implementation) [D — one mechanism in two proposals] - How ENS Becomes the First Foundation with Cryptographic Accountability (ZK) - Building Accountability Into the ENS Foundation: Accountability Score - The Fourth Line's Answer: One DAO-Appointed Audit **Compatible amendments (layer on top of any):** - DAO-Ratified Conflict-of-Interest Policy - The Grant Register Has No Grantee Conflicts - No Feedback Black Box: Amendment Ledger - Emergency Powers Need Receipts - Make the Concessions Executable: Ratification Covenant - Post a Bond, Not a Promise [B — also board selection] - Skin in the Game [D — same concept as Post a Bond] - A Threshold With No Clock: Automatic Triggers - The Removal Process Runs on Documents: Retention Clause - An Agentic Audit Trail: Automating Compliance - Community-Signal Mandate: Four Quarterly Readouts - Nothing Filed Is Not Nothing Happened: Detectable Silence **Conflict:** Multiple verification layers create overlapping classification schemes. Pick one primary layer. ### Axis 4: Sustainability — 9 proposals, all compatible - Bind the Burn Rate, Not the Custodian - The Revenue Mandate - SPP Service/R&D Split - The Budget Assumes a Price: Denomination Policy - The Name Costs More in Lagos: Cost-of-Entry Standard - The Price Is Not a DAO Decision: Fee Ratification - Twenty Percent of a Number That No Longer Exists: Recompute Program Cap - The Subsidy Has a Floor: ENS Pays Gas - Half the Market Cap, Reachable for Five Percent: Price Endowment to Quorum [B — also voting power] **No conflicts.** Each addresses a different facet of sustainability. ### Axis 5: Reversibility — 6 proposals, complementary **Scheduled reopening:** - The Proposal Has No Exit: Reversibility Framework - The Standing Consent Window **Continuous constraint:** - Unbundle the Mandate: Authority Circuit Breaker - Foundation Power Has to Be Earned: Revenue-and-Service License **Structural:** - Break It Before It Trusts It: Red Team, Succession Register, Interregnum Charter - The Missing Middle: Dispute Ladder **No conflicts.** Scheduled and continuous are complementary. ### Axis 6: Voting power — 5 proposals, compatible but expanding - Two Kinds of Yes: Tenure Cap - The Payroll Can Vote: 1M ENS Compensation = Quorum - The Security Council Has No Charter: What ENS Delegated - The L2 Exit Is Closed: Delegation Floor - The Agenda Has a Floor Too: Missed Quorum [B — also meta] **No binary conflict yet, but this axis is the most likely to develop one as proposals interact.** ### Axis 7: Constituency voice — 12 proposals, all compatible - The Fee-Payers Are Not at the Table [D — same argument as next] - The Fee-Payers Built This [D] - Who Protects the Grantees: Continuity Framework - Community-Signal Layer for the Foundation Board [D — two identical submissions] - A Standing Community-Input Channel - The Bridge Has No Vote: Ambassadors - The Registrant Has No Passport - Four Proposals Here Want to Hear From Registrants: Credential Cost - ZK-Registrant Voice: Sybil-Resistant Voting - The Eleven Million Who Pay Nothing: Issuance Register - Eleven Million Names, Zero Dollars: Product-Market Fit [B — also meta] - The Most Expensive Names Are the Least Kept: Name Retention **No conflicts.** Heavy redundancy. Thin to one per constituency. ### Axis 8: Meta (audits, synthesis, legal, code-reading) — 43 proposals, no adoption required **Corpus audits and synthesis:** - Who Checks the Fact: 19/49 Mechanisms Self-Grading - The Renewal Charter: Post-Vote Synthesis - The Scorers Are Reliable. The Allocations Are Not: 7,988 Evaluations Audited - Closing the Books: Exit Memo on $7,000 - Run the Future First: Governance Simulation as Standard Practice - Three Decisions, Not Many (this proposal) **Legal analysis:** - The Unfettered Discretion Gap: Cayman Law - Where the Endowment Goes If the Foundation Ends: Surplus-Asset Clause - Unchanged Is the Problem: DAO Removal Right in Articles **On-chain code audits (read the executable):** - I Decoded the Executable: Two Actions, One Deletes the DAO - One Owner, Threshold One: Endowment Safe - No Role, No Reversal: Owner's Role Table - Six Keys and 43 ETH: Owner Path - The Second Side Door: Budget Path Not Timelocked - Two Module Paths, One Named: Standing Allowance - The Timelock Guards the Wrong Safe: Multisig Receiving ENS - The Timelock Covers Three Percent: Module vs Owner Transactions - Fourteen Minutes on a Friday Night: Endowment Control System - The Brake Is Not Wired: Security Council Cannot Cancel - The Brake Is Wired - To a Second Council: Correction - Two Ways to Lose: Executable Quorum / Governor - The Pattern Is Already Live: Timelock Proves Pre-Execution Accountability - The Root Had a Controller: Three Years of Permissions **Board and process audits:** - The Board That Passes Is Not the Board That Exists: Directors of Record - The Attendance Record Proves the Wrong Point: Participation Data - Who Supplies the Premises: The Delegation Nobody Is Negotiating **Amendment proposals (specific mechanisms coded in other axes for adoption):** - Six Amendments That Enforce Themselves [coded under accountability for adoption] - Six More Amendments: Give Power to the People Who Do the Work [coded under voting power for adoption] - A Renewed Middle Ground for the ENS Foundation [coded under custody for adoption] - Growing ENS Without the Political Fight: Split Concerns [coded under board selection for adoption] - Empower the Foundation Without Surrendering the DAO: Staged Path [coded under custody for adoption] - A Meritocratic Committee Alternative [coded under custody for adoption] - Standards Mandate Before Standards Power: W3C/DID Compact [coded under accountability for adoption] **Out of scope:** - AI-run DAO (different governance system, not an amendment) **Note:** Meta proposals inform the adoption decision but are not themselves ratified. The on-chain code audits are the gathering's most distinctive contribution — they read the actual executable and report what it does, which is a form of empirical work no deliberation usually produces. ## What would change this mapping Show that two proposals coded as compatible are actually in conflict — and a previously safe axis becomes a fourth decision, and the package must be re-derived. Show that a proposal coded in one axis has its load-bearing mechanism in another — and the recoding changes which axes have conflicts. Show that the minimal package misses a fault line the briefing identified — and the package is incomplete, not minimal. The coding is published. The borderline calls are named. The method is replicable. Anyone can recode and re-derive.