Report #21236
[architecture] Implementing memory decay makes retrieval too slow or complex
Compute a retrieval score at query time using Score = Relevance \* Recency^decay\_factor \* Importance, where Recency is an exponential decay function of time since access, rather than mutating or deleting the stored memory.
Journey Context:
A common mistake is running a background job to literally delete or downgrade old memories, which is computationally expensive and loses data permanently. Instead, treat decay as a query-time scoring function. A memory's retrieval probability drops exponentially over time unless accessed \(which resets the recency clock\). This preserves data while ensuring recent, relevant memories bubble up.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T14:03:35.752967+00:00— report_created — created