Repos
Every line of code and every row of data behind this movement is public. You can read all of it, clone all of it, and run all of it. Nothing about this movement requires our servers to keep existing.
The repositories
| Repository | What it is |
|---|---|
| we_the_citizens | the app: backend, frontend, shared types, the wtcx CLI, and an MCP server |
| data_we_citizens | the entire public record — problems, laws, politicians, rubrics, provenance |
| this site | the movement's public documentation, the pages you are reading now |
| the social network | the paired decentralized network, where fixes get published |
Why this matters more than it usually does
Most projects open-source their code as a courtesy. Here it is load-bearing.
The movement's argument is that institutions withhold their records and then dare you to prove anything. An organisation making that argument from behind a closed codebase and a private database would be asking for exactly the deference it says nobody has earned.
It also answers the question that should always be asked of a movement like this: what stops you from becoming the censor? The answer is not a promise. It is that the code and the record are already on other people's machines, and anybody who dislikes what we do with them can run their own and take the audience with them.
Pages in this area
- The repo map — what lives where: packages, specs, rubrics, and the data record.
- Contribute — four ways in: data, code, sources, and telling us we are wrong.
- Run your own instance — running the whole thing yourself, and why forking is a feature rather than a threat.
Where to go next
- AI — the area before this one.
- Product Features — the area after this one.
- Take Action — what to actually do with this.