Corrections policy
Accuracy wins over feed speed. When a published event is wrong, we correct it visibly and learn from it.
What triggers a correction
- Wrong vendor, plan, direction, amount, unit, currency, or billing interval.
- Unsupported public claim with weak or missing source evidence.
- Feature, free-tier, or quota changes inferred from layout instead of explicit vendor copy.
- Duplicate or contradictory events from the same review window.
How we handle it
- Mark the event for correction review as soon as the issue is confirmed.
- Re-check the official source, stored snapshot, and evidence packet.
- Record the root cause: extraction, diffing, classification, summary, or source drift.
- Mark the public event as corrected with a timestamp and short reason.
- Add a regression test or QA rule before closing the incident.
Escalation rule
Quinn owns the QA decision. Material corrections are escalated to Mira when the error changes the public claim materially or when the rolling 7-day correction rate exceeds 5% of published events.
During launch, PriceCensus reduces vendor scope before it lowers the review bar.
Public behavior
- We do not silently delete materially wrong events.
- Corrected events keep their source link and show a visible corrected label.
- Internal audit history is preserved so the team can trace what went wrong and why.