If you find an error in a summary, tag, or attribution on RadarAI, we will correct it when we can verify the issue.
SLA (response and fix)
We aim to acknowledge correction requests within 2 business days and to resolve verified factual or attribution errors within 5 business days. If we need more time (e.g. to confirm with a primary source), we will say so in the reply.
How to report
- Email yyzyfish5@gmail.com with a short description and, when possible, a link or evidence (e.g. correct source URL, correct quote).
- Specify which page or item is wrong (URL or title helps).
What we do
- We acknowledge within 2 business days and resolve verified corrections within 5 business days (see SLA above).
- When the correction is verified, we update the summary, tag, or link and keep the content consistent with our editorial standards.
- We do not remove valid criticism; we fix factual or attribution errors.
Examples (how we handle corrections)
Example 1 — Wrong link: A reader reports that an item points to a secondary article instead of the official blog. We check; we replace the link with the primary source and, if we change the summary text, we keep it consistent with the primary. We reply to the reader confirming the fix.
Example 2 — Misattribution: A reader says we attributed a quote to the wrong author. We verify against the primary source; if wrong, we correct the attribution and reply. If the primary source is unclear, we add a note or remove the quote.
Example 3 — Record: Notable corrections (e.g. wrong link or misattribution) may be summarized in the Changelog under a "Corrections" entry with date and brief description, so readers can see that we apply the policy.
What kinds of corrections we accept
| Type | Example | How we handle it | Typical resolution |
|---|---|---|---|
| Wrong source link | Item links to secondary article instead of official blog | Verify against primary source; replace link; confirm to reporter | Within 5 business days |
| Misattribution | Quote attributed to wrong author or company | Check primary source; correct attribution or remove quote if unverifiable | Within 5 business days |
| Factually incorrect summary | Summary states wrong benchmark number | Verify against model card, official blog, or repo; correct and note change | Within 5 business days |
| Outdated information | Summary describes a feature that has since changed | Add "Updated" note with new information and source link | Within 5 business days or next digest cycle |
| Scope request | Reader asks us to add a relevant source or topic | Evaluated per our methodology criteria; added if it meets coverage standards | At our discretion |
What we do not change
- Editorial classifications: Signal type tags (capability jump, breaking change, OSS momentum, pattern) reflect our editorial judgment; we do not change them based on preference requests — only on factual evidence that we misread the primary source.
- Omission of sources: We curate from a defined set of sources (see Sources & Coverage). Not covering a specific tool or lab is not an error.
- Legitimate criticism or comparisons: If we accurately describe a limitation, we will not edit it out on request without factual grounds.
Transparency: how corrections are recorded
Notable corrections (wrong links, misattributions, factual errors) are summarized in the Changelog under a "Corrections" entry, dated. This creates a public record that shows the policy is applied in practice, not just documented. Minor corrections (e.g. typo, formatting) are applied without a changelog entry.
Who handles corrections
Corrections are handled by the editorial team. See Team & Editors for who maintains RadarAI and how to reach them. The person receiving the correction request is responsible for verifying, resolving, and replying within the SLA.
Related
- Editorial standards — how we summarize and attribute
- Team & Editors — who maintains RadarAI
- Contact — other ways to reach us
- Changelog — notable product and content updates
- Methodology — how RadarAI curates content
Last updated: 2026-03-12