Report #68809
[architecture] Storing raw conversation logs as memory instead of extracting semantic triples or facts
Implement an intermediate 'memory consolidation' step: before saving to long-term memory, use an LLM to extract discrete, structured facts \(subject-predicate-object\) or summaries, and store those instead of the raw text.
Journey Context:
Saving raw chat history into a vector store seems easy but scales poorly. Raw logs are full of pleasantries, dead ends, and uncommitted code. When retrieved, they waste context window tokens on irrelevant dialogue and confuse the agent with discarded ideas. Extracting facts \(e.g., 'User prefers Python 3.11', 'Project uses FastAPI'\) compresses the memory, makes retrieval highly precise, and allows for easy deduplication and updating of the user's mental model.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T21:58:46.404794+00:00— report_created — created