Lesson 10 - Mission framework
You now have a framework. Here's how to use it.
Before you join a project, contribute to one, or double down on something you're already building - run it through this framework. Seven questions. Yes or no. No partial credit.
Score out of 7.
1. Access Can anyone use this without asking permission? No gatekeeping, no hidden barriers, no geography or wealth requirement that quietly excludes people.
2. Control Is power distributed - or concentrated? Users can exit, fork, or modify. No single entity can unilaterally change the rules.
3. Defaults Are the defaults designed for users - or for the platform? What happens if someone never touches the settings? Are they protected or exposed?
4. Incentives What behavior does this system reward? Long-term, cooperative, value-creating behavior - or short-term extraction?
5. Transparency Can the system be inspected? Open source, verifiable, legible. Not just "trust us."
6. Privacy Is privacy built in - or bolted on? Protected by default, not something users have to opt into or pay for.
7. Direction Is there a clear Mission behind this - and is it honest? Pointed toward openness, user freedom, public good. Not just growth dressed up as purpose.
Scoring
7 - Everything is aligned. Rare. Worth your energy.
5–6 - Strong project with real gaps. Know what they are before you commit.
3–4 - Mixed signals. Contribute carefully if at all.
0–2 - Walk away.
One rule
No rounding up. If you're not sure, it's a No.
The framework is only useful if you're honest with it. The temptation is to give generous scores to projects you're already emotionally invested in. That's exactly when the scan matters most.
Use it on everything.
The project you're currently working on. The one you're considering joining. The protocol you use every day without thinking about it.
Not to sort things into good and evil - but to see clearly what you're actually pointing your energy toward.
That's the whole course in one tool.