Why it matters
Source freshness asks whether the live document matches what the business practices today. AI knowledge can be freshly indexed yet wrong if the source itself drifted from reality.
How it works
Compare governed copies to live URLs, run spot audits with domain experts, and reconcile support macros with policy text.
Example
Nintendo weekly spot checks compare chatbot refund answers against the live Refund Policy page. A mismatch triggers immediate source review even if the index timestamp looks recent.
Common mistakes
- 1Assuming CMS publish equals operational truth
- 2No process when support macros diverge from policy
- 3Freshness checks only on head pages, not deep links
Your source changed. Your AI should know.
Track source freshness, detect changes, and review impact before answers drift.
Explore Source Maintenance