The Trinity Universe DAO Constitution.

Preamble

Why this document exists

We, the players, explorers, builders, and guardians of the Trinity Universe, establish this DAO Constitution so that:

• The Universe stays free from centralized control.
• The identity and progress of every Ship stay permanent and sovereign.
• The worlds we build endure beyond any single person, company, or era.
• Expansion, creativity, and fairness define the shared destiny.

We adopt this Constitution so the Trinity Universe may thrive as a self-governing, community-owned, ever-expanding on-chain galaxy. Adoption itself is Article VIII. Until that article is met, this text binds no contract.

Article I · Purpose of the DAO

Mission and scope

Section 1. Mission

• Protect the long-term stability and fairness of the Universe.
• Govern the expansion of planets and game modes.
• Manage the community treasury for the benefit of all players.
• Preserve the core identity and history of the Universe.
• Safeguard players’ progress, ships, and on-chain achievements.

Section 2. Scope of authority

The DAO is specified to hold authority over the planet registry, expansion planet approvals, season resets and parameters, badges and achievements, community-treasury withdrawals, official lore, and emergency responses to exploits or failures.

The DAO does not control individual Ship ownership, ship stats or history, or player wallets. Ship stats and history are specified as immutable inside TrinityCore. The DAO governs the Universe. It does not govern the players.

Article II · Core protocol immutability

TrinityCore and the ship

Section 1. TrinityCore

After the Genesis Period ends, as Article VI defines it, TrinityCore becomes non-upgradeable, immutable, and permanent. TrinityCore contains the ship registry, the planet registry, global XP and level, season identifiers, and core universe parameters. No entity, including DAO governance, may alter that core code after immutability.

Section 2. Protection of ship identity

Ship identity is the wallet. It is permanent. The DAO cannot modify ship stats directly, reset ships, remove earned achievements, change ownership, or freeze or delete ships. Ships are sovereign digital beings.

Article III · Planets

Internal worlds and external worlds

Section 1. Internal planets (0–99)

Internal planets are created during the Genesis Period and governed by the DAO after immutability. The DAO may set status (ACTIVE, LOCKED, RETIRED), max population, season scoring multipliers, and themes and lore. The DAO may not modify the core gameplay logic of an internal planet after Genesis.

Section 2. External planets (100+)

External planets live in separate contracts. They may bring new game modes, economies, adventures, rule sets, and stories. The DAO admits them through the planet registry, caps XP deltas, sets how far their stats are trusted, may remove or blacklist one, and approves cross-planet badges. External planets evolve the Universe. The DAO decides which become canon.

Article IV · Governance

Who votes, and on what

Section 1. Governing body

The DAO is composed of Ship Owners (identity), Token Holders (economic weight), and Veteran Multipliers (time).

Section 2. Voting power

Voting weight is specified as ShipPower + TokenPower + TenureBonus. ShipPower comes from global level, badges, achievements, and veteran status. TokenPower comes from governance-token holdings and is specified to grow slower than a raw balance, so a large holder does not own the vote. TenureBonus comes from how early a ship registered and how long it has been active. The hybrid is meant to resist whale capture, Sybil attacks, free-riders, and founder dictatorship.

Section 3. Proposal categories

• Expansion: add external planets, approve major expansions, introduce gameplay templates.
• Season: reset a season, allocate a prize pool, adjust XP multipliers.
• Lore: canonize a story, name a planet, define a shard’s culture.
• Treasury: fund builders, art, infrastructure, and marketing.
• Emergency: lock a compromised planet, pause an unsafe feature, cap XP deltas, quarantine a rogue expansion.

Article V · Treasury

Where funds come from, and who may spend them

The treasury is specified to grow from marketplace fees, cosmetic sales, expansion planet registrations, tournament events, donations, and revenue shared by external creators.

Funds may be used for game development, art and lore, security audits, marketing, player reward pools, and infrastructure. Every expenditure requires DAO approval. This site holds no such treasury.

Article VI · Genesis Period

Temporary founder power, then surrender

Section 1. Duration

Genesis runs from Universe Launch until the first of these: 100 internal planets are full, 10,000 ships are registered, or the DAO passes a Genesis Completion proposal.

Section 2. Founder powers

During Genesis a founder multisig may upgrade TrinityCore and alter internal planet parameters, for bug fixes, stability, and bootstrapping.

Section 3. Surrendering power

When Genesis ends, the founder multisig is removed from the core contract, the core becomes immutable, and the DAO assumes governance. The Universe is then decentralized.

Article VII · Amendments

What a supermajority may change

This Constitution can be amended only by a DAO supermajority of at least 67 percent, with a two-week timelock and a public review period.

These clauses stay even against a supermajority: ship ownership rights, TrinityCore immutability after Genesis, the permanent existence of planets 0–99, the ban on altering a ship’s past history, and the ban on DAO authority over player wallets.

Article VIII · Adoption

When this document becomes active

This Constitution becomes active when it is ratified by at least 51 percent of voting power, the Genesis Universe has launched, the initial internal planets exist, and the first 1,000 ships have registered. None of those four conditions is met on this site. The flight game can register a ship in its book. That book is not this ratification.

Closing declaration

Community-owned, when the article says so

Let the Universe grow by the united will of the community that inhabits it. Let ships travel freely. Let planets rise and fall. Let creativity expand outward. Let no one hold the keys to destiny.

This is the Trinity Universe. Community-owned. Eternal. Ever-expanding. Those sentences are the aim of the draft. They are not a description of a deployed DAO.

The program that was saved with this draft

Source on disk, stubs in the executor

The drop-in program is trinity_dao. The Genesis variant is genesis_dao. Parameter structs and the account map for a future CPI live under sketches. Notes on why the source cannot be deployed are in the DAO readme.

• Voting power in the saved program is a square root of a token balance. Ship power and tenure are not wired.
• The quorum check compares cast votes with themselves. It does not measure eligible voting power.
• Execution does not require the vote to have passed. The handlers return success and move no account.
• The square root uses floating point. That is not a deterministic on-chain weight.
• Genesis execution still asks the founder key to sign, and then marks the proposal executed without a CPI.
• The placeholder program ids are not valid pubkeys. No key was generated for this draft.

The older index entry for reviewers, Pandora objects, and dust remains on the manifest. That design is a different note. It is also not a live vote.