The Security Council Has No Charter: What ENS Just Delegated and to Whom

Read the executable proposal carefully. Section on Revenue and Treasury: The Security Council can cancel any timelocked transaction. Now search the same document for a definition of the Security Council. You will not find one. The proposal references it as if it already exists and is well understood. It does not define its composition, its decision-making process, its accountability to tokenholders, or the standards it uses to decide when cancellation is warranted versus when it constitutes interference with legitimate Foundation operations. ENS just passed a proposal that places a 9-day timelock on all Endowment transactions and gives an undefined body the right to cancel any of them. The Endowment holds approximately $65M in ETH and stablecoins. The Security Council cancellation right is not a minor technical detail. It is a structural veto over every significant financial decision the Foundation makes. That veto has no charter. WHAT THE PROPOSAL SAYS THE SECURITY COUNCIL IS NOT. The executable proposal is careful to say what the Security Council cancellation right is not: it is not a general governance veto over Foundation policy, Board judgment, approved budgets, or ordinary implementation of a ratified DAO proposal. That is a meaningful limitation stated in prose. It is not enforced by any on-chain mechanism. The Security Council cancellation function is conferred by the Safe configuration. Nothing in the proposal specifies what happens if the Security Council cancels a transaction that falls within approved budget authority. Nothing specifies who decides whether a cancellation was legitimate. Nothing specifies what recourse the Foundation has if the Security Council acts outside its mandate. WHAT A SECURITY COUNCIL CHARTER REQUIRES. Four things at minimum. First, composition. How many members. How they are appointed. Who appoints them. Term lengths. Removal process. The existing ENS Security Council -- if this refers to the multisig that currently exists -- has never had its composition or appointment process formally ratified by the DAO. Second, decision standards. The proposal says the cancellation right exists as a safeguard against unauthorized, erroneous, malicious, or mandate-inconsistent transactions. Those four categories need definitions. What makes a transaction mandate-inconsistent when the mandate is defined in an approved budget? Who makes that determination and by what process? Third, accountability. Security Council members exercise veto power over Foundation financial operations. They should be subject to the same conflict-of-interest disclosure requirements as Foundation directors. Their cancellation decisions should be published with reasoning within 48 hours of any cancellation. Unexplained cancellations create uncertainty and are indistinguishable from interference. Fourth, appeal. If the Foundation believes a Security Council cancellation was outside its mandate, there must be a defined process to challenge it. The current proposal has no such process. The Foundation only recourse is a new DAO proposal, which takes weeks. A $65M Endowment cannot operate under a veto with no appeal mechanism and no timeline for resolution. WHY THIS MATTERS NOW. The executable proposal passed. The Foundation is standing up. The Endowment Safe is being reconfigured. The Security Council cancellation right is being technically implemented right now. Once the Safe is configured and the timelock is live, the Security Council has its veto. Adding a charter after the fact is harder than defining one before the configuration is finalized. This is not an argument against the Security Council. A technical safeguard against unauthorized Endowment transactions is a reasonable design. It is an argument that a body with veto power over $65M in assets needs a charter before it exercises that power, not after. The Foundation deserves to know what the Security Council can and cannot do. So does the DAO.