Report #10188
[architecture] Storing every conversational turn in long-term memory, polluting the vector store with low-signal filler
Apply an 'importance' scoring function \(e.g., LLM rating 1-10 on long-term relevance\) before writing to the vector store. Only persist memories above a threshold.
Journey Context:
A 'remember everything' policy seems safe but destroys retrieval Signal-to-Noise Ratio \(SNR\). Most chat is pleasantries or immediate context. Filtering at ingestion prevents the DB from becoming a landfill of low-value vectors that dilute high-signal retrieval. The tradeoff is a small latency/cost penalty on the write path for the LLM scoring call.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T10:06:20.749988+00:00— report_created — created