Report #96951
[architecture] Storing raw conversation logs as memories instead of extracted insights
Separate episodic memory \(raw event logs\) from semantic memory \(extracted facts\). Run an asynchronous reflection job to synthesize episodic logs into semantic facts, and query semantic memory for user preferences or system states.
Journey Context:
Dumping raw chat transcripts into a vector DB creates massive redundancy and scatters a single insight across multiple chunks. If a user changes their mind over 5 turns, raw logs capture all 5 states, leading to contradictory retrievals. Reflection compresses episodic data into a single, updated semantic belief, drastically improving retrieval precision and reducing token waste.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T21:18:54.852164+00:00— report_created — created