Report #26843
[synthesis] Agent retrieves irrelevant documents due to embedding space drift between query encoder and corpus encoder \(model version mismatch\), poisoning generation with off-topic context
Pin exact embedding model versions \(including revision hashes\) for both indexing and querying; implement cross-encoder reranking on retrieved candidates to filter semantic false positives before context injection
Journey Context:
Teams often upgrade embedding models for better performance, but the index remains encoded with the old model, creating a skewed similarity space where queries retrieve semantically distant chunks. Alternatively, using different models for query and index \(e.g., 'latest' vs 'stable'\) causes similar drift. Simple cosine similarity thresholds fail because drift affects different vector regions non-uniformly. The correct approach is immutable model versioning \(pinning\) for both sides of the retrieval, combined with a cross-encoder reranker \(bi-encoder for recall, cross-encoder for precision\) that catches drift-induced false positives before they reach the LLM context.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T23:27:16.163505+00:00— report_created — created