Projects · all optional
The Projects
The movement is three ideas: software should be free, stewardship should be rewarded, and human attention is precious. The projects below are experiments in putting those ideas into practice. None of them is required to take part. You can agree with the manifesto, make the charter's commitments and never touch any of these tools.
Current state for each one, with evidence and dates, is on the status page.
First priority: test the economics
| Project | What it's for | Where it stands |
|---|---|---|
| Stewardship pilot | Find out whether someone can earn a living from free software without making anyone dependent on them | Proposed, not started |
We built tools before testing the economic idea. That order is now reversed: new technical work should wait until the pilot shows what stewards and customers actually need.
Free code: anyone can continue the work
| Project | What it's for | Where it stands |
|---|---|---|
JRCv1 and jrc |
A detailed, voluntary standard and an offline tool for showing that a project can survive without its creator | Draft standard; the tool works |
| Adopt | Check a public repository against JRCv1 and get a list of what's missing | Works; still being reviewed |
| The Challenge | Ask an outsider to rebuild and run a project with no private help | Open; nobody has completed it yet for this project |
Rewarded stewardship: honest, accountable money
| Project | What it's for | Where it stands |
|---|---|---|
| Quartermaster | Open books for stewards: a ledger format and validator for costs and revenue | Ledger format and validator work; no billing integrations |
Human attention: let software do the busywork
| Project | What it's for | Where it stands |
|---|---|---|
| Agent access (WebMCP, MCP server, CLI, static API) | Let any AI agent read and check the project for people, without tying them to one AI provider | Works; native WebMCP still to be verified in a browser |
| AT Protocol records | Portable, user-controlled records for adoptions, assessments and contributions | Draft Lexicons; nothing published to the network |
| Canonical project identity and decentralized updates | A durable identity for a project and update channels no single host controls | Ideas only; nothing built |
How a project joins this list
Propose it in the debate. It should serve at least one of the three principles, be usable without the others, and say honestly what works and what doesn't.