Report #88974
[frontier] Agent memory retrieval returns factually correct but temporally or causally irrelevant facts due to pure vector similarity matching
Implement content-addressable memory where memories are nodes in a temporal graph with vector embeddings \(content\) and directed edges \(causal/temporal links\); retrieve via vector similarity to seed the query, then traverse temporal edges \(walk forward/backward in time\) to surface related events that occurred before/after the seed, not just semantically similar ones
Journey Context:
Simple vector RAG treats memory as a bag of documents, missing episodic sequences \(e.g., 'user changed password' is related to 'user cannot login' by time, not semantics\). Production agents are moving to associative memory graphs—similar to GraphRAG but for agent state—where activation spreads along temporal edges. This captures episodic context \(what happened after X\) and causal chains. Tradeoff: storage complexity \(graph DB overhead\) and query latency \(multi-hop traversal\) vs. retrieval relevance. Essential for agents with >100 turn history or complex task dependencies.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T07:56:00.049074+00:00— report_created — created