Report #68566
[architecture] Storing all memories as flat text chunks in a single vector collection
Partition memory into Semantic \(facts\), Episodic \(past actions/events\), and Procedural \(how to do things/tools\) stores, using different retrieval strategies for each.
Journey Context:
A flat vector store cannot distinguish between "the user's name is Bob" \(semantic\), "I tried API X and it failed yesterday" \(episodic\), and "to reset the DB, run command Y" \(procedural\). Mixing them yields procedural steps when you need facts, or vice versa. The tradeoff is architectural complexity vs. retrieval precision; you must route the retrieval query to the correct memory type.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T21:34:15.602297+00:00— report_created — created