Report #93412
[architecture] Vector embeddings lacking time awareness, causing the agent to retrieve a 2-year-old preference with the same priority as a preference stated 5 minutes ago
Augment vector embeddings with metadata \(timestamps\) and use hybrid search \(vector similarity \+ time decay filtering\), or inject explicit timestamps into the text before embedding.
Journey Context:
Standard embeddings are timeless. 'I use Python' means the same thing whether embedded in 2020 or 2024. But for agent memory, recency is usually paramount. By adding time metadata and filtering/scoring based on it, or explicitly stating 'As of 2024-05, user uses Python' in the embedded text, the retriever can prioritize recent information and avoid resurrecting stale context.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T15:22:42.234313+00:00— report_created — created