1.  [](/)
2.  [Diagrams](/diagrams)
3.  MUVERA: Why Query and Document Are Encoded Asymmetrically

[Back to Diagrams](/diagrams)MUVERA / Multi-Vector

# MUVERA: Why Query and Document Are Encoded Asymmetrically

Why Query and Document Are Encoded Asymmetrically

![Documents fill empty buckets with a mean; queries sum and leave empty buckets zero: the asymmetry is what makes the FDE dot product approximate Chamfer / MaxSim.](/diagrams/muvera-query-doc-asymmetry.webp)Full screen

Why Query and Document Are Encoded Asymmetrically

The trick that makes MUVERA's fixed vectors approximate Chamfer similarity is that queries and documents are encoded differently. A document has ~100 token vectors, so most buckets are occupied: each bucket takes the mean of its tokens, and any empty bucket is filled from the nearest non-empty bucket (by Hamming distance), so every possible query token is guaranteed a document-side neighbor to match against. A query has only ~10-30 token vectors, so most buckets are empty: each bucket takes the sum of its tokens, and empty buckets stay zero, an absent query token must contribute nothing. Written out, FDE(q) · FDE(d) = sum over buckets of (sum of query tokens) x (mean of document tokens): summing on the query side adds one term per query token, which is the shape of Chamfer / MaxSim, where each query token is scored against an estimate of its nearest document token. Doc-side fill guarantees that estimate exists; query-side zeros guarantee nothing spurious is added.

## Where this diagram appears

*   [Guide: Late-Interaction Retrieval (ColBERT, ColPali, MUVERA) →](/guides/late-interaction-retrieval)

Run this on your own data

Mixpeek turns video, images, audio, and documents in your object storage into searchable, timestamped results through one API.

[Search your own data](https://studio.mixpeek.com/namespaces/create?mode=managed&utm_source=homepage&utm_medium=diagram_detail&utm_campaign=mvs_onramp)

## Related diagrams

[

![A variable-size set of token vectors becomes one fixed-size vector via SimHash bucketing, projection, and repetition: no neural encoder required.](/diagrams/muvera-fde-pipeline.webp)

MUVERA: How a Multi-Vector Set Becomes One Fixed Vector



](/diagrams/muvera-fde-pipeline)[

![Tier 1 FDE-encodes the query and does fast single-vector ANN over all N to get a top-K; tier 2 reranks only those K with exact Chamfer over the original token vectors.](/diagrams/muvera-two-tier-retrieval.webp)

MUVERA: Two-Tier Retrieval (Cheap FDE Recall, Exact Rerank)



](/diagrams/muvera-two-tier-retrieval)[

![Recall@100 versus final FDE dimensionality on nfcorpus with ColBERTv2, log x-axis, one line per swept knob (k\_sim, d\_proj, r\_reps); r\_reps dominates at low dimensionality, d\_proj floors near 16, and k\_sim saturates past 5.](/diagrams/muvera-recall-ablation.webp)

MUVERA: Which Knob Actually Buys Recall (FDE Dimensionality Ablation)



](/diagrams/muvera-recall-ablation)