Report #5014
[architecture] When is a vector store the wrong choice for agent memory?
Use vector stores only for fuzzy semantic lookup of unstructured facts; use structured stores for exact state, ordered sequences, and relational data.
Journey Context:
Teams often default to a vector database for all memory, but vectors are poor at exact counts, identifiers, temporal ordering, and multi-hop joins. A realistic agent memory stack is polyglot: a structured database for state and relations, a vector index for semantic similarity, and the context window for working memory. The mistake is choosing one store for everything instead of matching the storage abstraction to the access pattern.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T20:30:33.981459+00:00— report_created — created