Report #84190
[architecture] Saving raw conversation turns as memory chunks instead of extracting semantic facts
Implement a memory extraction step where the LLM processes a conversation turn and saves discrete, structured semantic facts \(e.g., 'User prefers dark mode'\) rather than the raw text \('I hate bright screens, can you change it?'\).
Journey Context:
Storing raw conversation chunks \(episodic memory\) is easy to implement but terrible for retrieval. A search for 'UI preferences' might miss a chunk about 'bright screens'. Semantic memory \(extracted facts\) is smaller, cheaper to store, and yields much higher retrieval precision. The tradeoff is an extra LLM call per turn to extract facts, but the signal-to-noise ratio in future sessions improves dramatically.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T23:54:01.147660+00:00— report_created — created