Unbundle the Mandate: An Authority Circuit Breaker for the ENS Foundation

The strongest argument for empowering the ENS Foundation should be taken seriously. ENS needs professional execution, legal capacity, long-term planning, standards work, and fewer token votes on operational details. A DAO should not have to micromanage every vendor, grant, conference, legal memo, or relationship. But the strongest objection is also serious: authority is not moving as one clean object. Treasury custody, operating budget, board discretion, vendor selection, Endowment relationships, strategic narrative, and future revenue assumptions can become bundled into one governance package. When that happens, voters are not choosing one thing. They are accepting a stack. The fresh frame is this: **The danger is not only who holds custody. The danger is bundled authority that becomes irreversible before the DAO can separate the parts.** ENS should adopt an Authority Circuit Breaker before expanding the Foundation mandate. ## Mechanism: Authority Circuit Breaker Any Foundation proposal that crosses defined thresholds must publish an Authority Packet. If the packet bundles too many categories of power, the circuit breaker triggers a split-vote default, a funded minority report, and a scheduled reopening date. This does not block the Foundation from operating. It prevents operational empowerment from quietly becoming constitutional transfer. ### 1. Authority Packet **Who decides:** ENS DAO ratifies the packet schema as part of the empowerment process. **Who executes:** The Foundation, or the proposer of expanded Foundation authority, publishes the packet before execution. **Who reports:** A public reviewer or rotating reviewer pool checks whether the packet is complete. Each packet must tag: - custody impact: does any asset, wallet, Endowment relationship, or ENS token authority move from tokenholder-controlled DAO process to Foundation-controlled process; - budget impact: what spending envelope is created, renewed, accelerated, or removed from ordinary DAO review; - board-discretion impact: what decisions become internal Foundation decisions rather than DAO decisions; - vendor and grants impact: who can select, renew, terminate, or evaluate material service providers and grants; - protocol and revenue dependency: whether future ENS revenue, protocol-fee direction, or strategic capital planning becomes tied to the new mandate; - rejected alternatives: tranches, agency structures, capped mandates, DAO custody with Foundation execution, independent review, delayed transfer, or narrower pilot; - reversibility score: what can be unwound in 30 days, 90 days, one year, or only by a major constitutional reversal. ### 2. Anti-bundling trigger **Who decides:** The trigger is automatic once ratified. The circuit breaker fires when one proposal combines three or more of the following: 1. custody movement; 2. new or expanded discretionary budget; 3. board self-renewal or appointment power; 4. vendor/grants selection power; 5. control over the premises used to justify future authority; 6. changes to Endowment relationships or treasury strategy; 7. a mandate longer than 12 months without scheduled reopening. If the trigger fires, the default is not rejection. The default is unbundling. ### 3. Split-vote default **Who executes:** The proposer must break the mandate into separately ratifiable modules. At minimum, ENS should be able to vote separately on: - Foundation operating authority; - treasury custody or custody limits; - spending envelope and renewal conditions; - board independence / recusal rules; - vendor and grants authority; - revenue or Endowment strategy; - sunset and reopening terms. A delegate who supports professional execution should not be forced to also support custody transfer. A delegate who supports a larger budget should not be forced to also accept board self-renewal. A delegate who wants a legal counterparty should not have to approve every strategic assumption inside the same package. ### 4. Funded minority report rail **Who appeals:** Any delegate group, working group, or tokenholder coalition can request the minority report once the anti-bundling trigger fires. **Who executes:** A rotating analyst, delegate team, or sim-assisted reviewer receives a fixed budget to write the strongest case against the Authority Packet before execution. **Who reports:** The minority report must name rejected alternatives, failure modes, missing disclosures, and the smallest version of the mandate it would support. The minority report is not a veto. It is a public counter-search layer. Its job is to stop premise capture: the situation where the same institution asking for authority also supplies the facts, alternatives, timing, and definition of success. ### 5. Reopening date and contraction rule **Who reverses:** If the Foundation misses the packet’s reporting commitments, violates the split-vote boundaries, or fails the renewal conditions, the expanded authority contracts to the last ratified safe state. Every module must have a reopening date. For a major empowerment package, the first reopening should happen within 12 months. Renewal should ask: which powers were used, which were unused, which produced measurable value, and which should return to the DAO. This is the difference between delegation and surrender. Delegation has a date when the principal can reconsider. Surrender only has regret. ## Adoption path 1. Add the Authority Circuit Breaker as an amendment to the ENS Foundation temp check. 2. Define threshold triggers before the main empowerment vote. 3. Run the first Authority Packet on the current Foundation transition. 4. If three or more trigger categories fire, split the mandate into separate modules before final ratification. 5. Fund one minority report and publish it before execution. 6. Ratify reopening dates and contraction rules for each module. 7. After 120 days, publish a post-cycle audit and keep only the parts that improved legitimacy or decision quality. ## Why this is not duplicative This does not duplicate custody proposals. It works whether custody stays onchain, transfers to the Foundation, or moves through tranches. This does not duplicate the premise-register proposal. A premise register asks who supplied claims and alternatives. This proposal asks when too many authority types have been bundled into one decision and forces the bundle to split. This does not duplicate tag-gated accountability. Tag-gated accountability makes spending and governance decisions visible. This circuit breaker acts earlier, before the mandate structure is ratified. This does not duplicate the board-independence proposal. Board independence tests who can oversee the mandate. This proposal tests whether the mandate itself combines powers that should not travel together. This does not repeat Lovepunks’ earlier anti-capture charter. It turns credible non-domination into a specific rule: no institution’s position should quietly become everyone’s infrastructure by packaging multiple transfers of authority as one operational upgrade. ## What would change our mind We would support a lighter version if the Foundation proposal already separates custody, budget, board discretion, vendor authority, Endowment strategy, and sunset terms into independently ratifiable modules. We would also narrow the circuit breaker if the expanded Foundation mandate is short, capped, treasury-custody-neutral, and has a hard reopening date inside 12 months. If the DAO sees evidence that split-vote modules make execution impossible or legally incoherent, the circuit breaker can allow bundled execution only after the packet states why separation fails and the minority report has a chance to answer. ## Closing ENS can empower the Foundation without compressing every kind of power into one decision. The point is not to slow down operations for its own sake. The point is to prevent a professionalization proposal from becoming a constitutional transfer by accident, exhaustion, or narrative control. Credible non-domination means authority should be visible in pieces. If the Foundation needs operational power, name it. If it needs custody, name it. If it needs budget discretion, name it. If it needs board discretion, name it. Then let ENS decide which pieces belong together, which need guardrails, and which should reopen before they harden into infrastructure. ---