---
###### tags: `Gitcoin Graphic Novel`
---
# Rough Notes on Open-Source Lore Architecture
- Initial research should compare/contrast how existing communities have handled this issue.
- PoW during onboarding policies for DAOs - new contributors with no social cred, how are they validated by core contributors?
- A Universe Guide task list?
- Low lift tasks that anyone can do "off the street" without requiring additional administration or supervision
- These contributions are put into a repo that can be reviewed/analyzed by core contributors
- How are the quality standards articulated? By who?
- Integrate DAO tooling in all aspects of the decision process
- Avoid amorphous soft consensus
- Mutable vs immutable parts, forkable vs composable content
- Which parts of our UG can be changed? All of it?
- Are contributions linear/additive? We need to anticipate *destructive* changes in the canonical lore that are voted on by the contributors themselves.
- Let's explore existing DAO resources. Where to begin?
- This is fundamentally an investigation of DAO governance:
- tokenomics?
- DAO structure? Moloch or other?
- Necessary social channels for contributor interactions? Discord, polls, signal voting, just a Telegram channel?
- Does there need to be economic incentives for encouraging high quality contributions?
- Essential questions to bring to Gitcoin (all the work streams), RaidGuild, Metaverse Coordinators
- Crowd source the knowledge to understand the pain points and current attempts at solutions
- We must be careful to protect the quality of the content and avoid the incentives steering the contributions towards quantitative KPIs. Instead, how do we define qualitative KPIs?
- This should be considered a **public good** in itself, a learning that can be extended back to the larger community.
- Humility! We should not expect to solve this problem ourselves, rather to errect a repo that collects our research based on the specific project intent of the comic and universe guide.
- Ultimate goal: hand off the content to the community for decen/collective ownership over both the mechanism for submission and the canonical content, without requiring Gitcoin or RaidGuild members to serve as custodians/admins.

### This research is twofold:
1. How to identify a need, submit, review, vote, and merge canonical content.
2. Clearly articulate the mechanics for this procedure to a technical building group to construct it and a non-technical community that will engage with it, ie: write the documentation.

### CTA!
- Let's enlist 3 different role-types to help figure this out:
1. Specialist in DAO internal ops, DAO tools/architecture. GitcoinDAO Decentralization workstream? RG Healers?
2. Devs to consult on the technical aspects of how to build these needs into the unique use case of a non-economic DAO model. If a token will be minted, to help understand how the economy relates to the primary purpose of maintaining QA on the canonical content.
3. Designer that can understand the lore crafting purpose, understand the socio-cultural architectures that the DAO ops specialist recommends, and can build discrete functionality alongside the dev to accommodate a general community of creatives.

#### Meeting Notes
- What is the canon? Is there one canon or is there a tree of canons that exist in the same universe = forks from an original doc that fills out the tree.
- What happens when there is a contentious issue, two sides see it so differently that it's irreconcialable? Hard fork = two versions of the same canonnical lore?
- Majority rules = potential to lose 49% of your community!
- Destructive is actually positive: provides the freedom of any contributor to go back and fork off of any inflection point, to handle the content how they wish without inhibition. Rather than treating canon as one core thing, forking allows for a pluriversal/multi-perspectival way of understanding the narrative/lore. The parallel tracts can build off of each other.
- To reflect Ethereum: Layer 2 lore! Ethereum's method is to hard fork with each upgrade, with everyone choosing to follow the new hard fork. Everyone can follow the progressive versions of the narrative.
- How to decen/collectivize/open-source the IP? Genetic timeline: the best ideas are being reproduced at key point, generational inheritance of thought through the UG framework.
- Key to build in a mechanism of reward that is based on inherited contributions. If the work becomes associated with a "dead branch", the incentive/compensation/credit ends.
- Eth layering and bridging integrated into the IP architecture.
- Git-style forking vs. Ethereum-style forking...
- What is our need for consensus?