Report #102084
[architecture] Agent blindly trusts bad retrieved context and repeats wrong answers
Add an explicit reflection step after retrieval: ask whether the retrieved context actually answers the question before generating. If not, reformulate the query, retrieve again, or admit ignorance.
Journey Context:
Self-RAG showed that models can learn to emit reflection tokens evaluating retrieval usefulness. In production you can implement this with a simple verification prompt. The classic failure is 'we retrieved it, so it must be true', which makes the model rationalize around irrelevant or outdated context. The tradeoff is an extra LLM call, but for high-stakes memory use the accuracy gain is worth the latency.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-08T04:56:43.868471+00:00— report_created — created