Challenge a Claim

This project's whole method rests on being checkable and correctable — see How We Reach Conclusions. This page is where a reader actually does that, not just reads about the principle.

Every submission is reviewed by a named human against the same sourcing standard applied to everything else on this site — the same one described in the methodology page and enforced document-by-document in the Sources Register. It is not published or acted on automatically. If it leads to a change, that change is logged in the Update Register with the reason — the same place every other correction to this site is recorded.

Submitting a structured challenge requires the same free registration used to back a proposal — a verified name and district, not an anonymous form. That's a deliberate choice, not friction for its own sake: a challenge that changes a published argument carries the same standard of accountability this project asks of everything else on it.

What Happens Next

A submission here does not publish or change anything automatically. Per How We Reach Conclusions, a claim is corrected only after the evidence behind it is actually checked — the same standard applied whether the challenge comes from a reader, a fresh research pass, or new data being published. Claims that don't survive that check get corrected. Claims that do survive it stay, and the reasoning for keeping them can be explained on request.

This is a deliberately lean first version of the full challenge mechanism described in Platform Integrity. It's real — submissions are structured, attributed to a verified registration, and reviewed by a named human — but it doesn't yet include the identity verification or AI-assisted triage the fuller version calls for; both depend on external services not yet set up. What matters most works today: a challenge can be submitted, and if it's right, the content actually changes.