Report #62291
[architecture] Storing raw conversation turns as long-term memory instead of extracted facts
Run an asynchronous extraction pipeline on conversation turns to generate semantic triples or factual statements \(e.g., 'User prefers dark mode'\). Store these extracted facts in the vector DB, not the raw transcript.
Journey Context:
Storing raw chat history in a vector DB leads to redundant, conflicting, and highly contextualized chunks that lack standalone meaning. Extracting facts normalizes the data, making it universally retrievable and preventing the agent from hallucinating past conversational context into new, unrelated tasks.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T11:02:21.950003+00:00— report_created — created