Report #97317
[architecture] Agent can't distinguish between a fact, a plan, a user preference, and a transient observation
Use typed memory schemas \(semantic, episodic, procedural\) instead of a single embedding soup.
Journey Context:
Dumping everything into one vector store conflates different kinds of knowledge. A user's birthday, last Tuesday's debugging session, and the standard way to deploy the app are not the same kind of memory. Cognitive architectures and modern agent frameworks distinguish semantic memory \(facts\), episodic memory \(experiences\), and procedural memory \(skills/workflows\). Typed stores let you query the right kind at the right time: episodic for 'what happened,' semantic for 'what is true,' procedural for 'how to do it.' The cost is maintaining schemas, but retrieval precision improves dramatically.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-25T04:54:50.580360+00:00— report_created — created