---
###### tags: `Gitcoin Graphic Novel` `GitcoinDAO Metaverse Coordinators Group` `RaidGuild`
---
# Metaverse Coordinators Work Stream (MCWS) Governance Model

#### Gitcoin DAO is the mother DAO, layer 1
- Streams funds to the Captain DAO's shared minion.
- Expects clear KPIs for funded projects. Holds Captains accountable.
- Serves as the canonical source for community principles.
#### MCWS Captains are the sub-DAO, layer 2
- Receives funds from Gitcoin to shared minion.
- Votes on funding proposals made to minion by Contributors.
- Provides QA on canonical lore from Gitcoin DAO.
- Screens/vets proposals for overall quality, canon alignment, value-add, and speculative potential.
- Responsible for generating, identifying, articulating, and supporting new directions for the whole work stream.
- Initial Captains for summoning DAO:
- Kevin
- Coltan
- Travis
- Additional/replacement Captains can be added via standard membership proposals.
#### MCWS Contributors form sub-sub-DAOs via [Yeeter](https://twitter.com/nowdaoit/status/1461756680128151560?s=20), layer 3
- Any contributor can submit a signal proposal to the Captains DAO through a standard template:
- Project Description
- Value-Add (for Gitcoin and/or public goods)
- Deliverables
- Team Members
- Budget/Ask
- If the signal proposal passes, the Captains will summon a [Yeeter](https://twitter.com/nowdaoit/status/1484577489837903872) with at least 1 Captain holding majority voting shares in the DAO along with the project team. This ensures:
- Collusion protection: the Captain can block malicious proposals
- Open-access funding: anyone can contribute to kickstart the project (not just Gitcoin DAO), so the project retains a high amount of autonomy.
- Social accountability: anyone that funds the project and later disagrees with the team's decisions can ragequit their loot shares.

#### Scenario:
1. You discover the MCWS and join the tg group.
2. You have an idea to create super cool Gitcoin DAO key chains based on the metaverse lore.
3. You create a proposal to the Captains DAO describing your project, how it will raise lots of funds for public goods, how all of the 1000 keychains will be unique, the roles of contributors, and how the money will be spent.
4. The Captains vote to pass the signal proposal and spin up a Yeeter for the Gitcoin Metaverse Keychains project and deposit funds.
5. (optional) You shill your keychains around the ecosystem and raise even more money than you asked for from Gitcoin/MC.
6. When the funding goal is reached, a DAO is auto-magically summoned with the 3 team members holding 49% shares and 1 Captain representing 51% shares. The Captain share holder retains accountibility for the success of the project.
- Various endings....
A. (Best outcome...) You make your keychains with the money you received and make your mark on the Gitcoin universe. Everybody wins.
B. (In an alternate universe...) One of your team members submits a funding proposal to drain the DAO treasury before completing the keychains. The Captain blocks the proposal and ragekicks the malicious member. The project continues until completion.
C. (In an alternate dimension...) The keychains are revealed to be a thinly veiled ponzi scheme, upsetting Gitcoin DAO and the funders. The Captain blocks all funding proposals and encourages all funders to ragequit their loot shares, draining the DAO of it's treasury and ending the project.

## Governance Model for the Universe Guide

- A project DAO (Stewards of the Universe?) is summoned for the Universe Guide contributors with the 3 Captains and a Gitcoin delegate holding majority shares. Additional membership is permissioned so this majority holding is always maintained.
- The Universe Guide is collectively owned IP that belongs to the members of the DAO (and by extension Gitcoin for holding majority shares). Ragequitting shares forfeits rights to the lore.
- Anyone can submit "Canon Proposals" (see below) to fork or change lore. There is no quarom, so even a single vote will pass the proposal.
- [Additional elaborations on the Universe Guide can be found here.](https://hackmd.io/@TravisWyche/H1K2cap3K)

## Democratic Open-Source Lore for the Universe Guide
- Currently thinking of this as a boost to a Moloch-style DAO via the DAOhaus interface, but other protocols might be considered.
- A "boost" (supplement) might be developed with the following considerations:
- Currently any DAO member can change the metadata on their DAO (via the DAOhaus interface). This is a signed txn.
- This metadata includes text description, tags, images, etc.
- If this txn can be passed through a proposal, members could vote on changes to collective DAO assets.
- We can apply this functionality to other DAO assets, such as editing text documents, making PRs to a project repo, or changing symbols of a visual design system.
- "Canon Proposals" (essentially a signal vote) allows lore changes to be member permissioned and archived on-chain.