Report #95027
[architecture] Storing all agent memories in a single flat vector collection
Partition memory into Episodic \(timestamped events\), Semantic \(facts/knowledge\), and Procedural \(skills/tools\). Use different retrieval and storage strategies for each.
Journey Context:
A flat vector DB treats a learned fact \('API endpoint is /v2'\) the same as an event \('I failed to deploy yesterday'\) and a skill \('how to write a test'\). Querying a flat store yields mixed types. Separating them allows the agent to query 'what happened' vs 'what is true' vs 'how do I do this' distinctly, drastically improving retrieval precision.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T18:05:05.772010+00:00— report_created — created