Report #9568
[architecture] Vector store accumulates contradictory facts over time
Implement memory upserts or state-based overwriting. When inserting a new fact about an entity, search for existing facts on the same entity/predicate and invalidate or delete the old one.
Journey Context:
Append-only vector stores are terrible for state changes. Because embeddings are static, appending a new fact doesn't invalidate the old one. When the agent queries 'Where does the user live?', it retrieves both 'NY' and 'CA' and gets confused. Using a hybrid store \(vector \+ relational/graph\) allows you to update the current\_location node rather than just appending a new location event. The tradeoff is increased complexity in memory writes \(must perform search-before-write\), but essential for maintaining factual consistency.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T08:36:16.509456+00:00— report_created — created