Report #70556
[architecture] Treating all memory as raw text chunks \(episodic\) makes it hard to answer generalized questions about user preferences
Split memory into Episodic \(raw events/interactions\) and Semantic \(extracted facts/preferences\). When an event is stored, run an extraction step to update the Semantic knowledge graph or fact table.
Journey Context:
Vector DBs store episodes. But 'Does the user like dark mode?' requires aggregating episodes. By extracting semantic facts \(triplets or key-value pairs\) from episodes, you enable fast, deterministic lookups for preferences, while keeping episodes for 'how did we do this last time?' queries.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T01:00:18.337514+00:00— report_created — created