Reporting an inaccurate claim

Every Brief paragraph, Forecast rationale, and Risk entry carries a "Report inaccuracy" button. Use it when a cited claim is wrong, when the citation does not support the claim, or when a more authoritative source contradicts it.

How to file

1. Click the small flag icon next to the paragraph or claim
2. Pick a reason — wrong fact, wrong citation, outdated, missing context, other
3. Add a one-sentence reason and (optional) a URL or document title for the correct source
4. Submit

The report routes into the inaccuracy moderation queue at /admin/inaccuracy-reports (visible to admins only). You get a confirmation toast and a ticket reference; the report does not affect what other users see until a reviewer acts on it.

The five-minute SLA

The platform's hard service-level commitment on inaccuracy reports is:

• Triage acknowledgement: 5 minutes. A reviewer confirms the report is in queue and assigns priority. Reports raise an alert to the review queue on receipt.
• First action: 30 minutes. Either the claim is retracted from the active Brief, the citation is repaired, or the report is dismissed with a published reason.
• Public retraction notice: 4 hours. Any retracted claim produces a brief.retracted webhook event and an entry in the audit log.

The five-minute SLA is the headline number because the trust contract with users depends on it. SLA performance — including misses — is measured and surfaced in the SLO dashboard at /admin/slo.

Roadmap, not shipped: automated incident paging for SLA misses. There is no paging integration in the product today. A miss is visible on the SLO dashboard and reaches the team by email.

What happens to a retracted claim

A retraction does three things:

1. The active Brief is updated. The paragraph carries a strikethrough on the retracted sentence and a "Retracted [date]" footnote pointing at the moderator note.
2. The audit log records it. Anyone with audit-log access (Government tier and Enterprise+ admins) can see the full retraction trail.
3. A brief.retracted webhook fires. Configured Slack / Teams / Discord receivers get a card with the brief ID, the retracted sentence, and the reason.

What a retraction is not

A retraction is not a deletion. The original claim and citation remain in the database for audit. The Brief surface is what gets updated.

When to use this versus the support widget

Use "Report inaccuracy" when there is a specific claim or citation that is wrong. Use the support widget ("?" in the bottom-right corner) when the issue is broader — the Brief did not arrive at all, the export is broken, a feature is missing, billing is wrong.