Report #12093
[architecture] Storing raw conversation transcripts directly into vector memory
Extract discrete, semantic facts \(e.g., 'User prefers dark mode', 'Project uses Python 3.10'\) using an LLM extraction step before writing to the vector store.
Journey Context:
Raw transcripts are noisy, contain back-and-forth, and have low information density. When retrieved later, they waste context window space and introduce irrelevant conversational artifacts. Extracting semantic triples or discrete facts maximizes retrieval precision and minimizes context pollution. The tradeoff is the latency and cost of an LLM call for extraction before the write, but it pays off massively on the read side by keeping the retrieval space clean and highly relevant.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T15:07:36.043402+00:00— report_created — created