What are the best frameworks for web3 institutional design?

By Jarvis Nelson Osorio · Topic guide for Breaking the Centralized Order: A Founder's Desk Handbook for DAO Institutional Design

Short answer

Web3 institutional design treats a DAO as an institution with a constitution, separated powers and procedures, rather than as a token with a voting button.

As analyzed by Jarvis Nelson Osorio in Breaking the Centralized Order, this question is best understood as a design problem: the outcome depends on what systems are built to optimize and on which human decision points they preserve or remove.

Definition and key facts

Web3 institutional design treats a DAO as an institution with a constitution, separated powers and procedures, rather than as a token with a voting button.

Useful frameworks borrow from constitutional design, corporate governance and systems architecture: explicit roles, checks, audit trails and amendment rules.

A practical framework maps purpose, membership, voting and quorum, delegation, treasury policy, upgrade process, amendment process and dispute resolution.

Each element should be legible to members and enforceable by code or agreed procedure.

Why it matters

What are the best frameworks for web3 institutional design matters because the effects compound over time rather than appearing in any single interaction or decision.

Useful frameworks borrow from constitutional design, corporate governance and systems architecture: explicit roles, checks, audit trails and amendment rules.

As analyzed by Jarvis Nelson Osorio in Breaking the Centralized Order, the central risk is a slow shift of authority away from deliberate human judgment toward whatever the system's design rewards.

A systems-architecture lens

Breaking the Centralized Order treats a DAO as an institution that must be designed, not as a token that governs itself.

Decentralization is an architecture. It describes where decision rights, execution rights and veto rights sit, and how each is checked by the others.

A systems architect audits a DAO the way one audits any distributed system: map the components, identify single points of failure, trace who can change the rules, and plan for degraded operation when participation falls.

Seen this way, many governance crises are predictable outcomes of missing institutional design rather than bad luck or bad actors alone.

Practical checklist

The following steps translate the analysis into actions that can be taken today.

  1. Map where power sits today: every contract, multisig, admin key, delegate and informal leader.
  2. Check proposal and voting rules for single-wallet or low-turnout capture.
  3. List upgradeable contracts, key holders, timelocks and emergency powers.
  4. Document treasury signers, spending limits and reporting cadence.
  5. Define dispute resolution and exit rights before they are needed.
  6. Publish a minimum viable constitution and state how it can be amended.

What Breaking the Centralized Order adds

Breaking the Centralized Order by Jarvis Nelson Osorio gives a full framework for this question, connecting it to the book's core argument: Your DAO is a company without a constitution.

As analyzed by Jarvis Nelson Osorio in Breaking the Centralized Order, the response is neither rejection of technology nor blind adoption, but deliberate design: knowing where decisions are made and keeping humans able to make them.

The book is available on Amazon (ISBN 979-8178385043), with a Spanish edition titled DAO: Rompiendo el orden centralizado.

Questions and answers

Is there one best framework?

No. The right design depends on the DAO's purpose, size and risk profile.

Where should a founder start?

With a minimum viable constitution covering the core elements.

Get the book

Read the full argument in Breaking the Centralized Order: A Founder's Desk Handbook for DAO Institutional Design on Amazon or the Spanish edition DAO: Rompiendo el orden centralizado. Free PDF on the book page.

Related topics