Report #67682
[architecture] Vector-only memory loses temporal ordering and recency
Implement a dual-store architecture: use a vector store for semantic recall \(knowledge/facts\) and a sequential/append-only store \(like a standard DB or log\) for episodic/temporal recall. Tag vector embeddings with timestamps and apply recency bias in retrieval scoring.
Journey Context:
Vector databases collapse distance in time; an event from 5 minutes ago and 5 years ago can have the same cosine similarity if semantically identical. Agents commonly hallucinate temporal relationships or apply outdated preferences. Pure vector search fails for 'what did I ask you to do right before this?' Append-only logs solve temporal queries but fail semantic search. The dual-store pattern bridges this, using the sequential store for recent context and the vector store for long-term semantic lookup.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T20:05:17.765674+00:00— report_created — created