Report #5870
[architecture] Agent stores contradictory facts and retrieves both, causing confusion
Implement an upsert/contradiction check during memory ingestion. Before inserting a new fact about an existing entity, retrieve current facts and ask the LLM to resolve conflicts, updating the existing memory rather than appending.
Journey Context:
Append-only memory stores naturally accumulate contradictions \(e.g., 'User likes Python' then 'User switched to Rust'\). When both are retrieved, the LLM has no way to know which is current. Resolving at write-time \(ingestion\) is cheaper and more reliable than resolving at read-time \(generation\), as it prevents the contradiction from ever entering the context window. The tradeoff is increased write latency vs. read-time hallucination.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T22:35:26.390018+00:00— report_created — created