MoreRight — The DAO
Every platform.
Scored. On-chain. Accountable.
The DAO's mandate is continuous, community-powered accountability of every significant digital platform. You score it. We canonicalize it. The data goes on-chain. The methodology is open. The data is the product.
What the DAO does:
Scores are submitted by the community via the Chrome extension or the Score tool. Each score runs through the void-scoring pipeline (evidence synthesis → formal analysis → automated council check). The DAO canonicalizes scores that survive consensus validation. Canonical scores go on-chain (Solana). API sales distribute earnings back to contributors who scored that platform, weighted by accuracy.
What the DAO cannot do:
Vote on the scoring methodology. Change the three void conditions (opacity, responsiveness, engagement). Override kill conditions. Modify CC-BY 4.0 papers. The mathematics is inside the Most Holy — not on the voting surface. Arrow's theorem does not apply to math.
Scores are submitted by the community via the Chrome extension or the Score tool. Each score runs through the void-scoring pipeline (evidence synthesis → formal analysis → automated council check). The DAO canonicalizes scores that survive consensus validation. Canonical scores go on-chain (Solana). API sales distribute earnings back to contributors who scored that platform, weighted by accuracy.
What the DAO cannot do:
Vote on the scoring methodology. Change the three void conditions (opacity, responsiveness, engagement). Override kill conditions. Modify CC-BY 4.0 papers. The mathematics is inside the Most Holy — not on the voting surface. Arrow's theorem does not apply to math.
How a Score Becomes Canonical
01
Submit
Community submits a platform via extension or Score tool. Pays $0.50 in USDC.
02
Pipeline
domain-analyzer + paper-writer + validate.py runs. Council auto-check grades A–D.
03
Consensus
Score compared against other submissions. Outliers flagged. $MORR holders vote on disputes.
04
On-Chain
Canonical score posted to Solana. Contributor earns USDC when API sales reference that score.
DAO governs
- Which scores get canonicalized
- Treasury USDC allocations
- Bounty rates (custodian-set, appealable)
- Platform queue priority
- Contributor dispute resolution
- Weekly scoring challenges
Cannot be voted on
- The three void conditions (opacity / responsiveness / engagement)
- The 26 kill conditions
- Scoring methodology (CC-BY — irrevocable)
- Dissolution pre-commitment (Solana)
- CC-BY papers (open forever)
- The Constraint-Custodian Theorem
How Earnings Work
| Action | Trigger | Payout |
|---|---|---|
| Score validated | Score matches consensus, survives council check | % of API sales for that platform, in USDC |
| First Scout | First contributor to score a platform | 2× earnings multiplier on that platform |
| Disconfirmation accepted | Falsification of existing score accepted by council | 3× standard bounty in USDC |
| Weekly challenge | Complete the custodian-set weekly scoring challenge | Bonus multiplier on category scores that week |
| Article published | Scored platform → article → passes council quality check | Fixed USDC bounty from treasury |
All payouts in USDC. Treasury sells $MORR → USDC automatically. Contributors never need to hold, trade, or think about $MORR. The seed incentive pool (7% of $MORR supply) covers contributors before API revenue scales. Earnings % is custodian-set and adjustable.