Report #94030
[architecture] Agent retrieves two contradictory memories and hallucinates a compromise or picks the wrong one
When retrieving memories, fetch multiple \(e.g., top 5\) and include their timestamps. Add a system prompt instruction to resolve conflicts by deferring to the most recent timestamp, or explicitly ask the user for clarification if timestamps are close.
Journey Context:
Vector search returns by semantic similarity, so contradictory facts often cluster together. LLMs struggle with conflicting context and often average them out or pick the first. Alternatives: deterministic deduplication before prompt injection \(hard, requires exact match or LLM judge\). Best call: expose the temporal metadata to the LLM so it can do what humans do—trust the latest information.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T16:25:04.636418+00:00— report_created — created