Foundation
Three-Layer Governance
How Oumafy separates constitutional, operational, and project governance so the network can resource work at the speed of execution without collapsing legitimacy into one vote or one cap table.
Summary
One-person-one-vote protects constitutional legitimacy but cannot resource fast-moving operational decisions. Project-level cap tables resource work but cannot set constitutional limits. The three-layer model lets each governance question travel to the layer that can actually answer it — with traceable voting keeping all three layers honest to each other.
Why three layers
A network the size of Oumafy has three fundamentally different governance questions running at the same time. What is legitimate for the whole network to be or do? How should the network allocate operational bandwidth, attention, and capital across many simultaneous initiatives? And who owns the upside inside any individual venture?
Trying to answer all three with the same mechanism fails in predictable ways. Pure one-person-one-vote cannot resource operational work fast enough and creates decision fatigue. Pure cap-table governance cannot set constitutional limits and invites extraction. Pure appointed leadership cannot hold legitimacy over time.
Three layers, with clear boundaries between them, is what lets a civilization-scale network move without breaking.
The constitutional layer
The constitutional layer answers: what is Oumafy allowed to be?
One verified Passport, one vote. Opt-in participation. Zero Day Rules are immutable. Treasury principles, eligibility rules, and the limits on what the other two layers can decide all live here. This is the legitimacy floor of the network.
- One member, one vote, opt-in per proposal.
- Zero Day Rules are the immutable ethics layer (no riba, no haram industries, transparent governance).
- Sets the hard limits that the operational and project layers cannot cross.
- Slower on purpose — constitutional change should be rare and visible.
The operational layer
The operational layer answers: how should the network allocate shared capacity right now?
Qualified self-selection with traceable voting. The people with relevant context — operators building in a given cluster, AutoPilot stewards, Foundation program leads — make operational decisions about bandwidth, prioritization, and Foundation funding. Every decision is signed, traceable, and auditable by the constitutional layer.
- Qualified self-selection — decisions are made by members with relevant proven context.
- Traceable voting — every operational vote is recorded and auditable across time.
- AutoPilot bandwidth allocation, AI HR prioritization, Foundation funding calls.
- Fast enough to match real-world execution cadence; bounded by constitutional rules.
The project layer
The project layer answers: who owns the upside inside an individual venture?
Contribution-weighted cap tables. Project-level strategy. The ordinary equity governance that any functional startup uses, with the addition of the 2.5% Foundation stake that ties project success back to the commons.
- Contribution-weighted equity within a project.
- Project-scoped strategy and roadmap decisions.
- 2.5% Foundation stake in every venture — the structural covenant to the commons.
- Bounded by the operational layer (where Foundation resources are coming from) and the constitutional layer (what the project is allowed to be).
The iceberg reframe
A common concern about multi-layer governance is that a small group ends up making most decisions while most members feel excluded. The iceberg reframe addresses this directly.
Roughly 10% of the network is deeply involved in operational decisions at any given time — the operators, stewards, and program leads with real context. The other 90% set the rules those operators work within, audit what the operators do, and retain constitutional authority over the whole structure.
Traceable voting is what keeps the iceberg honest. Every operational decision is signed and auditable. Every constitutional vote by the 90% can override an operational decision by the 10% if the operational layer crosses a constitutional limit.
Appeal path
Any member can escalate an operational decision to a constitutional vote if quorum is met. Any constitutional vote can override any operational decision. Project-level governance is bounded by both.
This is the explicit escape hatch that keeps the three-layer model legitimate over time.
- Minimum quorum for constitutional escalation — small enough to be reachable, large enough to prevent noise.
- Constitutional override authority over any operational decision.
- Clear records of what was decided, by whom, at which layer, and with what appeal history.
Published before it is needed
This documentation exists to make the governance model legible to the network, to investors, and to incoming operators before any governance crisis requires a ruling. Publishing the model up front is the condition under which the other two layers stay bounded.