Practical AI Radar Editorial Policy
Our pages are written to help readers make practical decisions. We separate source-backed facts from judgment, mark claims that can age, and avoid publishing recommendations that depend on unsupported numbers or vague authority.
Source Standards
Every article keeps visible source anchors for official docs, public repositories, product pages, government or standards pages, or other primary references when a claim depends on them.
Freshness Checks
Prices, versions, star counts, compatibility claims, subscriptions, and policy-sensitive details are treated as time-sensitive. They must be refreshed before important updates, product links, or paid promotion.
Commercial Boundaries
Ads and future affiliate links do not decide recommendations. If a page later receives a product link, the link must support the article's existing decision criteria and disclosure.
Corrections
Readers can use the contact page to flag outdated sources, unclear comparisons, or claims that need a narrower source. Corrections should improve the article rather than simply add more text.
AI Radar Specific Rules
AI Radar does not treat GitHub stars, trending rank, or social attention as product proof. Repository popularity is used as a research cue. A publishable review still needs workflow context, setup risk, maintenance signals, source links, and a clear reason a builder should test, wait, compare, or skip.