Report #21078
[architecture] Storing raw text or chat logs into the vector store leading to poor retrieval granularity
Before persisting to long-term memory, use an LLM to extract structured memory objects \(JSON with keys like type, entity, fact, timestamp\) and embed the extracted fact, not the raw text.
Journey Context:
Embedding raw text like 'User said: I hate the color blue, please change it' retrieves based on conversational noise. Embedding the extracted fact 'User preference: dislikes color blue' is dense, highly retrievable, and unambiguous. The tradeoff is the upfront cost of the extraction LLM call and the risk of the LLM dropping nuance, but for long-term memory, structured extraction drastically improves signal-to-noise ratio.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T13:47:36.133235+00:00— report_created — created