Report #14651
[architecture] Saving every single action or observation to long-term memory fills the database with low-value noise making high-value memories impossible to find
Force the LLM to score the 'importance' of a memory \(1-10\) before saving it. Only persist memories above a certain threshold, or use the score to weight retrieval alongside recency and relevance.
Journey Context:
Disk space is cheap, but retrieval attention is expensive. If 99% of memories are trivial \(e.g., 'opened file', 'printed log'\), the embedding space becomes saturated with noise, pushing high-signal decisions out of the top-K results. By explicitly scoring importance at the time of encoding, you ensure the retrieval space is dense with high-value information.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T22:10:33.458505+00:00— report_created — created