Report #30239
[architecture] Storing entire conversational turns or large document chunks directly into long-term memory, causing noisy retrieval and wasted context window space
Extract atomic, semantic triples \(Subject-Predicate-Object\) or discrete facts from episodic interactions before saving to long-term memory. Keep raw logs in a separate, cheaper episodic store only if full replay is needed.
Journey Context:
Raw text chunks contain filler, conversational pleasantries, and multiple intertwined facts. When retrieved, they waste the context window with irrelevant surrounding text. Extracting atomic facts maximizes the density of the context window. The tradeoff is the upfront LLM cost of extraction, but it pays dividends in retrieval precision and context efficiency.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T05:08:40.407451+00:00— report_created — created