Governing ourselves into obsolescence

An institution that builds infrastructure for self-governing organisations has to answer one question before anyone else asks it: how does it govern itself? I first answered it in December 2025, and the answer has held even as the dates moved. This is that answer, cleaned of its first timetable.

I. The paradox

One of the seven Nexi the Foundation works on is autonomous governance: infrastructure that lets an organisation move from hierarchical control to distributed decision-making, progressively and safely.

The Foundation itself started the way foundations start: an Italian non-profit with a board.

The paradox is plain. How can we build governance infrastructure we do not use ourselves? How can we argue for sovereignty while practising hierarchy? How can we ask anyone to trust infrastructure we do not trust with our own decisions?

We cannot. If we believe in what we are building, we have to run on it first.

II. Why a DAO

The answer is a DAO, the Forge DAO, as the coordinating layer of governance across the Foundation's work. I have five reasons, and the last one is the one that matters most.

It tests our own thesis. The governance Nexus claims that organisations can decentralise progressively, safely and effectively. If we do not do it ourselves, there is no reason for anyone to believe it works. Every success is evidence; every difficulty becomes a lesson we can publish.

Participation without borders. A foundation is bound to a jurisdiction: an Italian non-profit serves Italian donors, and board seats go to people who can meet. A DAO can give a developer in Lagos the same voice as a supporter in Milan. For infrastructure meant to serve people everywhere, that is a requirement.

Aligned incentives. In a traditional organisation, users are customers, donors are patrons, team members are employees, and each has different incentives. When contributors govern, everyone's incentives point at the mission, and taking part means shaping the infrastructure instead of only using it.

Time. I expect organisations governed this way to become ordinary well before the decade is out. Learning how to do it early is cheaper than converting a legacy structure late.

The exit, built in. This is the reason that matters. Every founding institution has an exit problem: founders want to step back one day, and the mission has to survive them. Who takes over? How is the purpose preserved? Where does the institutional memory live? A DAO answers with exit to community: governance decentralises step by step, the community takes increasing ownership, the founders step back without collapse, and continuity is part of the structure.

Our goal is to make ourselves obsolete: the infrastructure governed by the people who use it, and running without us.

III. A path, walked in steps

Nobody flips a switch from a board to a DAO. In December 2025 I drew the path in four phases.

Advisory. The DAO's votes are recommendations; the board keeps full legal authority. The mechanisms get tested where mistakes are cheap.

Hybrid. The DAO controls defined decisions, grants and support to ventures among them; the board keeps a veto on critical matters.

Transition. The DAO holds the majority; the board concentrates on compliance and the legal wrapper; the founders can begin to step back.

Autonomous. Full DAO governance, with the board kept only for emergencies. The Forge becomes a protocol more than an organisation.

The first timetable put the advisory phase in 2026. It moved. The Foundation's programme now sets the start of decentralised governance as a threshold for 2027 and half of it for 2028, and the Forge DAO itself is planned for 2027–28. What the phases describe has not moved: the order, and the rule that each step is earned by the one before it.

IV. The legal shape

"DAOs are not legal entities" was the first objection in 2025, and it is answerable. The plan is a Swiss association: a non-profit form under Swiss law, with governance written into its articles, legal personality to hold assets and sign contracts, and protection for participants. Switzerland has the most developed legal framework for this, a neutral jurisdiction and a strong rule of law.

There is a second reason for Switzerland, specific to us. An Italian third-sector entity is not the right body to carry this kind of governance, and so the Foundation will not become the DAO. The DAO coordinates; the legal entities operate, each with its own governance for local compliance. The detail of that relationship is still being designed, and I will not pretend here that it is settled.

V. What this is not

Some boundaries need saying in the first person.

This is no investment opportunity. Governance is participation in a mission, never in a profit. Nobody is raising money by selling a voice in decisions, and nobody is promising returns.

This essay announces no instrument. How participation will be recorded is a question with legal and regulatory rules of its own, and it will be treated separately, properly, when it is ready.

This keeps the law in place. DAOs and legal entities coexist: the association gives legal personality, the national entities handle local compliance. Distributed governance augments legal structure.

This is slow on purpose. Progressive means progressive.

VI. The risks I accept

Honesty about the difficulties is part of the design.

Regulatory uncertainty. This is pioneering ground and the rules move. The answer is a conservative start, a sound legal wrapper and counsel engaged early.

Gridlock. Distributed decisions can be slow, and some decisions cannot wait. The answer is clear proposal frameworks, emergency procedures and delegation, the same mandate logic the essay on treasuries describes.

Low participation. If people do not take part, governance fails quietly. The answer is simple tools, education and many ways to participate.

Mission drift. A community could pull the institution away from its purpose. The answer is a small set of locked principles, an ethics function, and, in the early phases, a board that can still say no.

Technical attack. Contracts have bugs and governance can be attacked. The answer is the verification the essay on proof argues for, applied to our own contracts first.

Each risk is real. None of them is a reason to keep the hierarchy forever. An institution that cannot imagine its own obsolescence will spend its energy preventing it, and I would rather spend ours building something that outlives us.