Report #8466
[architecture] Agent searches semantic memory for how to do X instead of episodic memory for how I did X last time
Separate memory stores into Semantic \(facts, e.g., 'API endpoint is /v1/data'\) and Episodic \(past action trajectories, e.g., 'To query the API, I first had to get the token, then retry 3 times'\). Query episodic memory for task planning and semantic memory for factual grounding.
Journey Context:
When an agent needs to solve a problem, it often searches its vector DB for the problem description. It might find a fact related to the problem, but not the sequence of actions that successfully solved it. People treat all text as equal in a single vector store. The tradeoff is that maintaining two stores increases system complexity. However, cognitive architectures distinguish between 'knowing what' \(semantic\) and 'knowing how/when' \(episodic\). Retrieving a past successful trajectory \(episodic\) provides a much stronger plan for the agent than retrieving disconnected facts.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T05:37:51.788876+00:00— report_created — created