Contribute

Contribute to the record

The highest-value contribution and the one that needs the least setup. Fix a wrong row, add a missing source, add a channel for somebody whose record is thin, close a gap the coverage page already names.

You can do this through the app or as a pull request against the data repository. Both land in the same review.

Contribute code

Standard open-source flow. Worth knowing before you start:

• Read the spec for the surface first. The pm/ directory usually explains why something is the way it is, and a good number of the obvious improvements were tried and retired for reasons that are written down.
• The hard rules are enforced by tests. If a check fails the build over something that looks pedantic — a tool name inside a string, for example — that is the rule working, not a bug.
• Specs and code move together. A behaviour change that leaves its spec stale is half a change.

Contribute an assessment rubric

The sixteen qualification rubrics are files. They are the standard people get assessed against, and improving one is a direct contribution to the fairness of every assessment that follows.

The bar: a rubric level must be reachable by people who disagree about policy. If only one political position can score a 9, the rubric is broken and the movement wants to know.

Tell us we are wrong

Genuinely a contribution, and the one the process is most carefully built around. Every decline comes back with a stated reason you can read, nothing is silently dropped, and nothing is hard-deleted — what the movement was asked and chose not to do stays part of its record.

If you have a stake in the outcome, say so and file anyway. Self-interest is labelled, never blocked.