Can verification separate structural near-misses from topical matches?

The retrieval-composition tension and the geometric constraint behind it suggest a clean architectural response: stop asking dense retrieval to do both jobs, and split the pipeline. Training for Compositional Sensitivity Reduces Dense Retrieval Generalization benchmarks this idea concretely. Pooled cosine handles recall — broad topical filtering across large candidate sets. A separate verifier handles identity-sensitive matching on the filtered candidates.

The benchmark compares verifier options operating on token-token similarity maps (the cross-product of query and candidate token representations). MaxSim — the late-interaction approach used in ColBERT-style systems — excels at reranking for topical relevance. It does not, however, reliably reject structural near-misses. A query that asks "did the dog bite the man" can still rank "the man bit the dog" highly under MaxSim because the token-level similarities are high regardless of structural role.

A small Transformer trained end-to-end on the token-token similarity maps reliably separates near-misses. The architecture is operating on a different signal than pooled cosine — the full pattern of token interactions rather than a compressed single vector — and the architecture is trained for a different task (verification, not retrieval). The combination changes what the system can reject.

The deeper structural move is that retrieval and verification are different problems with different geometries. Retrieval needs broad coverage and efficiency; verification needs structural precision. Forcing both into a single component is a category error that the dense-retrieval era has been working around with hard-negative training and architectural variants. The cleaner answer is to admit they are different jobs and assign them to different components.

For builders, this is an implementation pattern with immediate application. A production retrieval pipeline that struggles with structural near-misses (legal queries, medical specificity, role-sensitive search) should not try to fix dense retrieval — it should add a verifier downstream. The verifier can be small relative to the retrieval stage because it only runs on the filtered candidate set. The combined system performs better than either component alone.