01 / Three layers
Not every opinion needs the same power.
Community and DAO systems can surface ideas, preferences, risks and proposals. The Council reviews matters formally delegated to Founder governance. The Founder and MUTERRA Ltd retain safeguards and duties that cannot be delegated by a token vote.
02 / Council of 13
Twelve Bridge Seats. One Founder Seat.
The Council is intentionally small: closer to a compact strategic board than a mass-token parliament.
Bridge members bring independent judgment, experience, networks and perspective. The Founder occupies the thirteenth Seat and retains separate safeguard powers.
03 / Bridge
The best view on RAOLAX comes with responsibility.
A Bridge Seat is not only the most expensive badge. Members are expected to contribute judgment, introductions, strategic thinking and active participation when matters reach Council.
That is why Bridge is application-only and why active authority need not transfer automatically to an anonymous buyer.
04 / Published delegation
The Council can only touch what is placed inside its scope.
Possible delegated matters include major world or canon direction, important Founder asset programmes, selected MUTA ecosystem decisions, governance architecture, high-impact partnerships and important smart-contract rules.
The Council does not run payroll, routine hiring, production frames, taxes, banking, employment law, infrastructure security or statutory director duties.
05 / Proposal flow
Signal first. Responsibility after.
The public flow is simple: community signal → proposal → Council review → final text → vote → Founder action → implementation status.
Not every preference becomes policy. It becomes information governance is expected to consider and record.
06 / Voting
The bigger the decision, the more agreement it should require.
Ordinary matters can use a simple majority. Current design targets for major Founder-level matters and irreversible actions are 8 of 12 and 9 of 12 eligible Bridge votes respectively.
Those numbers remain design targets until the final Council Charter fixes the categories and procedure.
07 / Safeguards
A permanent brake, not a second steering wheel.
The Founder can block a course judged dangerous to the project’s survival, legal position or long-term direction, but cannot invent agreement and declare a personal proposal approved.
Emergency action is reserved for material legal, treasury, contract, infrastructure, IP or continuity threats and should leave a visible record and later review.
08 / Public record
Authority should leave evidence.
Proposals should create a readable history: discussion, final text, vote, Founder action and implementation status.
Years later, the useful question should not only be who held a Seat. It should also be what they argued for when it mattered.