Introduction

A reflection on the ENS Metagov retrospective: what the smallest legible set of operating documents looks like for a working DAO, and why a canonical policy inventory is the foundational reform from which the others follow.

Details

Timeframe2026

The legibility problem

A mature DAO operates through many entities. ENS has the DAO itself, the Foundation Board, ENS Labs, Working Groups, and delegates — each with accumulated policies, norms, and informal agreements that shape decisions in real time. The Metagov retrospective study mapped this surface in detail. What the mapping reveals is that the gap between we know how this works and we have a canonical inventory of how this works is exactly where governance dysfunction lives.

You can't reform what you can't see. Every new proposal arrives without context, every onboarded delegate rediscovers the same norms, and every audit produces the same surprised observations about how decisions actually get made.

Reading the retrospective

The Metagov work is structured as a chain — hypotheses about what's broken, data sources to test those hypotheses, findings derived from the data, and reforms that flow from the findings. Reading the report this way makes one thing obvious: many of the proposed reforms aren't standalone interventions. They're operationalisations of an underlying structural assumption — that the DAO needs a single, versioned source of truth about its own rules.

The Minimal Viable DAO

The smallest legible operating surface — what every DAO entity needs in writing for governance to be auditable rather than aspirational — is four categories of policy:

  • Foundational. Slow-moving, DAO-ratified. The constitutional layer. Changes via formal governance, infrequently.
  • Recurring. Quarterly reporting, scheduled reviews, periodic attestations. The cadence layer.
  • Event-based. Response protocols for incidents — security, legal, treasury, reputational. The contingency layer.
  • Accountability. Checks and balances across entities — who can challenge what, on what timeline, with what remedy. The separation-of-powers layer.

A DAO with these four categories ratified, versioned, and assigned to owners can be governed. A DAO without them is being governed by whoever shows up.

The forcing function

The retrospective proposes a Governance Advisor role to maintain this inventory — every policy with status, version, ownership, and a forcing function that ensures it gets reviewed when it should. The role is the cheapest part of the reform. The expensive part is admitting that until now, this inventory hasn't existed and the work has accumulated as tribal knowledge.

The "minimal" in Minimal Viable DAO is doing real work here. The goal isn't comprehensive policy coverage — that's a decade-long exercise. The goal is the smallest set that makes the DAO legible enough to govern itself.

Status

Published as a reflection on the ENS retrospective draft final report. This is one strand of a broader Lighthouse thesis: empirical accountability is a precondition for decentralized organisations to make decisions worth defending.

Topic

Governance Operations

Operating documents, policy frameworks, retrospective methods, and accountability structures that let DAOs govern themselves coherently.

Concepts