Why it matters
Lineage shows how knowledge flowed from origin through transforms to AI use. It answers whether a claim came from legal policy or a support rewrite.
How it works
Record transformations: CMS export, mirror, chunk, embed, retrieve, generate. Lineage graphs support incident analysis.
Example
Nintendo lineage traces a chatbot pro-rata statement to Help Center mirror of Refund Policy section 4, approved by legal, indexed June 2, retrieved in session abc123.
Common mistakes
- 1Broken lineage when content copied manually between systems
- 2Lineage without timestamps or actor IDs
- 3Treating lineage as optional for internal-only apps
Your source changed. Your AI should know.
Track source freshness, detect changes, and review impact before answers drift.
Explore Source Maintenance