Report #51179
[architecture] Vector database filling up with useless conversational filler and degrading retrieval
Extract structured atomic facts or knowledge triplets from the conversation before saving to memory. Do not embed raw conversational turns.
Journey Context:
Saving raw chat history into a vector store pollutes the embedding space with greetings, filler, and pronouns lacking antecedents. This destroys retrieval precision. By using an LLM to extract self-contained, discrete facts prior to embedding, you maximize the signal-to-noise ratio and ensure retrieved memories are immediately usable. The tradeoff is added latency and cost from the extraction LLM call, but it prevents retrieval collapse over long sessions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T16:23:38.889695+00:00— report_created — created