Report #95212
[research] Ignoring provided documentation in favor of outdated pre-trained knowledge
Implement a strict grounding check: if the provided RAG context contradicts your internal knowledge, strictly follow the context. Add explicit system instructions like 'If the provided documentation conflicts with your prior knowledge, defer to the documentation.'
Journey Context:
When RAG context conflicts with an LLM's strong parametric prior \(e.g., an old API version\), the LLM often ignores the context and generates the prior. This is the 'attention override' failure. Simply providing context isn't enough; the model must be explicitly instructed to prioritize the context over its internal weights.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T18:23:29.842239+00:00— report_created — created