Report An Error

Transparency only works when people can point out stale sources or unclear explanations.

Start here

Link-first correction path

This flow keeps reporting minimal. Use the page link below so the issue stays tied to the right page without asking for extra personal details.

No page link was passed in yet. Open this page from a bill or explainer page so the context travels with it.

What happens next

What we keep

Page URL and context if you came from a bill or explainer page.
A short note about what looked wrong or confusing.
No raw address requirement and no hidden public correction ledger yet.

What we do not keep

Raw description text is not stored in the receipt — only a boolean flag indicating a description was provided.
Raw email content is not stored — only a boolean flag indicating an email was provided.
No API keys, tokens, or session data are stored in correction reports.

Review process

What happens after you submit.

What you can report

Use this page for stale or wrong source links, confusing explanations, tone concerns, accessibility barriers, or AI output that feels unsupported.

What review should look like

Reports should be reviewed as product trust work. That can mean checking a source link, clarifying wording, tightening how uncertainty is shown, or flagging an AI explanation issue.

What this page does not promise yet

This page does not claim a public correction ledger or a fully built appeals system. It does promise that the site should make it easy to surface issues.

Helpful reports are specific

If you know the page, claim, source, or section that needs review, include it. The clearer the report, the easier it is to verify.