Built so it can't be bought.
Most "free" education projects stay free right up until someone decides it's worth more closed. Bluelearn is structured so that the mission outlives any individual, board, or funder: in the legal form, the money rules, and the safeguards we can't quietly undo.
The entity
A California nonprofit public benefit corporation.
The Bluelearn Project is incorporating directly as a nonprofit, not a startup that promises to be good, and not a project living under someone else's umbrella. The nonprofit form means there are no shareholders to enrich and no exit to optimize for. The only thing it's legally bound to serve is its public-benefit purpose: free, structured knowledge for anyone.
Two layers
The project and the knowledge are governed separately.
Deciding how the software gets built is a different job from deciding what's true in a guide. Bluelearn keeps those two responsibilities apart so neither one captures the other.
The project
How the platform itself is built: the codebase, the roadmap, technical direction. Decisions are made in the open on GitHub, with clear tiers of responsibility for proposing, reviewing, and merging changes. Stewardship sits with the project's maintainers and is documented as the organization formalizes.
The knowledge
What gets published and what stays. Content is governed by verifiers who review guides against a rubric before publication, and moderators who handle votes, reports, and disputes afterward. Expertise (not seniority in the org) is what qualifies someone to judge correctness. See the review pipeline →
Money
Funding has rules, and they're not optional.
How a project takes money decides what it becomes. These are the commitments money has to live inside:
No paywalls
The knowledge is free to read, always. Funding can never gate access to it.
No non-contextual ads
No surveillance advertising and nothing that turns the reader into the product.
Funding is public
Where the money comes from is published annually. No quiet donors, no hidden strings.
Editorial firewall
Funders don't shape content. The people who pay the bills can't decide what a guide says.
Entity before money
The formal nonprofit exists before significant funding is accepted, so there's an accountable structure to receive it.
Mission over growth
Money serves the public benefit, not the other way around. How to support it →
The locks
Safeguards that are hard to undo on purpose.
Good intentions don't survive a bad year. So the protections that matter most are being written into the organization's governing documents, designed to resist exactly the moment when someone wants to quietly walk them back.
Perpetual effectiveness
Core commitments are written to stay in force, not to lapse, expire, or be conveniently forgotten.
No sale of control
There is no equity to sell and no acquisition to accept. The project can't be bought because there's nothing to buy.
The knowledge base stays downloadable
The full corpus remains exportable. If the project ever broke its promises, the community could take the knowledge and leave. Recoverability is the ultimate check.
Capture triggers consequences
Attempts to corrupt the project (bribery, self-dealing) are tied to automatic governance consequences, not left to discretion.
Termination as a backstop
There are defined paths, including votes run on independent infrastructure, to remove people who act against the mission, so no single seat is unaccountable.
These safeguards describe the project's governing intent as it formalizes its incorporation. The binding language lives in the official governing documents, which take precedence over this summary.
Licensing
Open all the way down.
Both the software and the knowledge are licensed so they can never be locked away, including by us.
The code
Strong copyleft. Anyone can run, study, and modify the platform, and any hosted version must share its source. No one can fork it into a closed product.
The content
Every guide is free to share and adapt with attribution, under the same license. The knowledge stays in the commons permanently.
Contributions are made under a Developer Certificate of Origin, a lightweight sign-off confirming you have the right to contribute what you're submitting. Full terms are in the terms of use.
Governance only matters if it's watched.
Read the principles we hold ourselves to, or come ask hard questions in the open.