Report #14247
[architecture] Retaining all conversational utterances indefinitely, degrading retrieval precision
Apply a time-decay weighting to vector search scores and periodically run a curation background task to merge or delete low-access, high-age memory fragments.
Journey Context:
Not all memories are worth keeping. 'Pass the salt' doesn't need to be embedded forever. Without decay, the vector space gets polluted with trivialities, reducing the signal-to-noise ratio for future retrievals. Developers often avoid deleting data 'just in case,' but this violates the principle that memory requires curation to remain useful. Implementing a decay factor \(e.g., exponential decay based on timestamp, or access-count based reinforcement\) mimics human forgetting and keeps the memory store lean.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T21:08:47.866790+00:00— report_created — created