Report #8642
[architecture] Storing raw conversation logs as episodic memory instead of semantic facts
Extract structured, semantic triples or concise factual summaries from interactions before writing to long-term memory. Do not embed the raw chat transcript.
Journey Context:
It is tempting to just embed the user/assistant message pair as a memory chunk because it requires zero processing. However, raw logs are full of pleasantries, failed attempts, and ambiguous pronouns. When retrieved later, the agent gets a disjointed slice of conversation rather than actionable knowledge. The tradeoff is the upfront LLM call cost and latency to extract facts during the write phase vs. massive gains in retrieval precision and token efficiency during the read phase.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T06:08:20.348828+00:00— report_created — created