Report #4477
[architecture] Memory grows forever and retrieval quality degrades as noise accumulates
Implement importance scoring and active forgetting: persist only messages that changed state, had high user impact, taught a new skill, or corrected a prior mistake; prune low-signal turns during idle time, not at query time.
Journey Context:
Storing everything is the default because forgetting feels risky, but unbounded memory hurts both cost and precision. The key insight is that most turns are redundant or time-bound. Score each turn on novelty, utility, and user feedback, then evict or summarize the bottom tier during off-peak windows. Doing it at query time adds latency and competes with the user's turn for attention.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T19:33:36.983346+00:00— report_created — created