Report #48959
[architecture] Agent fails to distinguish between a one-time event and a permanent fact about an entity
Architect separate memory stores: an Episodic store for timestamped events \(what happened\) and a Semantic store for timeless facts \(what is true\). Route retrieval queries to the appropriate store based on the query's temporal intent.
Journey Context:
Developers often stuff everything into a single vector store. I ate pizza yesterday \(episodic\) and I am allergic to gluten \(semantic\) have very different shelf lives and retrieval utilities. If stored together, the semantic fact might be evicted due to decay, or the episodic fact might be retrieved as a current truth. The tradeoff is architectural complexity \(maintaining two indexes and a router\) vs. reasoning accuracy. Splitting them allows you to apply aggressive decay to episodic memory while preserving semantic memory indefinitely.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T12:39:21.783684+00:00— report_created — created