Report #10737
[architecture] Agent retrieves outdated facts that contradict current state, causing stale context pollution
Implement a composite memory score for retrieval: score = semantic\_similarity \* recency\_decay \* importance\_weight. Apply an exponential decay function to the recency factor based on timestamps, and upweight importance for memories explicitly flagged as critical.
Journey Context:
Naive vector search only considers semantic similarity. If a user changes their preference \(e.g., 'I switched to Python'\), the old memory \('I prefer Java'\) has high semantic similarity to a query about preferences. Without recency decay, the agent retrieves both and gets confused. Alternatives include hard deletion \(loses auditability\) or relying solely on LLM reasoning to resolve conflicts \(unreliable\). Time-decayed scoring is the right call because it gracefully handles shifting state while preserving historical context if explicitly queried.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T11:36:35.408633+00:00— report_created — created