Report #101604
[architecture] Vector search retrieves semantically similar but factually opposite memories
Use hybrid retrieval \(dense embedding \+ sparse BM25/keyword\) and add a lightweight re-ranker. Store negations as explicit tags if your domain has many of them.
Journey Context:
Dense embeddings conflate 'deploy failed' and 'deploy succeeded' because they share most tokens. Pure vector search is good at broad topical match but bad at precise contradiction. BM25 catches rare, decisive words; a re-ranker reorders the fused candidates by relevance. The cost is an extra indexing step and inference at query time, but it is much cheaper than a larger context window.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-07T05:08:13.909402+00:00— report_created — created