Report #28629
[architecture] Storing raw conversation logs as unstructured text chunks in vector store
Separate memory into Episodic \(raw events/turns, time-bound\) and Semantic \(extracted facts, entities, time-agnostic\). Extract semantic triples at write-time and store them in a knowledge graph, while keeping episodic logs in a time-indexed vector store.
Journey Context:
Searching raw logs for facts is noisy. 'I like pizza' said 3 months ago might be retrieved alongside an unrelated conversation about pizza delivery. By extracting semantic facts at write-time, you pay the LLM cost once, but retrieval becomes precise and multi-hop \(via graph traversal\). Episodic memory is kept strictly for 'how did we do X' questions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T02:26:50.956834+00:00— report_created — created