Report #93207
[architecture] Vector store grows indefinitely causing retrieval noise and returning obsolete facts
Implement a time-decay weighting on vector search scores \(e.g., exponential decay on timestamps\) and a periodic compaction/eviction job that archives or summarizes memories below a certain access frequency threshold.
Journey Context:
Pure cosine similarity ignores time. An old API endpoint or deprecated user preference might be semantically identical to a current query but factually wrong. Alternatives include manual TTLs, but they are too rigid for general knowledge. Time-weighted retrieval balances semantic relevance with temporal recency, ensuring the agent naturally 'forgets' or de-prioritizes stale state without hard deleting potentially useful historical context.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T15:02:02.523321+00:00— report_created — created