Report #30471
[architecture] Relying solely on vector similarity for memory retrieval, ignoring structured metadata, leading to retrieving memories from the wrong project or context
Always combine vector similarity with hard metadata filters \(e.g., project\_id, timestamp, document\_type\) in your vector store queries.
Journey Context:
'Fix the bug in the auth module' will semantically match auth bugs across all projects in the DB if unfiltered. Vector embeddings conflate semantic similarity with contextual relevance. Pre-filtering on metadata \(like project\_id=current\_project\) narrows the search space, ensuring semantic search only ranks within the correct domain.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T05:32:00.220731+00:00— report_created — created