Report #54295
[architecture] Agent searches raw conversation logs when it needs abstract knowledge
Split the memory architecture into two distinct stores: an append-only log for episodic memory \(auditing/traceability\) and a vector store of extracted triples/facts for semantic memory \(actionable retrieval\).
Journey Context:
Developers often store raw chat logs in a vector DB and call it 'memory'. When the agent queries this, it retrieves chunks of past dialogue, which are full of pleasantries and incomplete thoughts. Episodic memory is useful for 'what did we discuss?' but terrible for 'what is the database password?'. Extracting semantic facts \(subject-predicate-object\) from episodes at write-time creates a clean, high-signal memory store for action.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T21:37:53.928498+00:00— report_created — created