Report #3320
[architecture] Vector similarity retrieval returns irrelevant facts that derail the agent
Combine vector search with metadata filters and re-ranking; never rely on cosine similarity alone for agent memory retrieval.
Journey Context:
Pure embedding similarity confuses words that share semantic neighbors but have different intent \(for example, 'deploy' in Kubernetes versus 'deploy' in retail\). Production memory pipelines filter by conversation\_id, agent\_id, timestamp, and tool type first, then re-rank with a cross-encoder. Metadata filtering is cheaper and more precise than increasing top-k.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T16:30:34.537846+00:00— report_created — created