It Takes Two to Match: Co-Evolving Generative Retriever with Reinforcement Learning
Runpeng Dai, Kaili Huang, Changsung Kang, Ciya Liao
University of North Carolina at Chapel Hill · Apple
Published September 1, 2026 · on the feed September 3, 2026 · ▲ 68 · arXiv 2609.00638
The abstract
Retrieval is the first stage of modern search and advertising systems, selecting a candidate set from a large item universe for downstream ranking and auction. Recent work increasingly leverages LLMs to improve retrieval through query expansion, data synthesis, and retrieval-feedback training. However, the generative component is typically used for query-side augmentation, while final matching is still delegated to a downstream retriever. We introduce CoGR, a retrieval framework that instead trains LLMs to directly construct retrieval representations on both query and item sides. Each generator produces a compact set of keywords, which are matched directly through an inverted index, preserving compatibility with existing keyword-based retrieval infrastructure. CoGR uses a two-stage training pipeline. Supervised fine-tuning first establishes an aligned keyword space, after which co-evolving reinforcement learning alternately optimizes the query- and item-side generators with GRPO against the opposite side's frozen index. Both sides optimize the same query-to-item retrieval F_1 objective: the query side receives retrieval F_1 directly, while the item side receives a counterfactual marginal reward measuring the change in query-side F_1 caused by its generated keywords. Across 10 representative sparse, dense, and generative baselines, CoGR achieves the best performance on both an internal APP Marketplace dataset and the public WANDS benchmark, improving F_1 over the strongest baseline by 10.9% and 36.1%, respectively. Further analysis shows stable co-evolution and increasingly aligned query--item keyword spaces over training.
The Brief
2:40A short podcast summary of the paper. Written and voiced by AI.
Transcript
It Takes Two to Match. Co-Evolving Generative Retriever with Reinforcement Learning. By Runpeng Dai and three others, from the University of North Carolina at Chapel Hill and Apple. Published on the first of September. No code repository is linked to it.
In modern search and advertising systems, retrieval comes first. It selects a candidate set from a very large universe of items, and everything downstream, ranking and auction, works from that set. Language models are increasingly used to improve this stage, through query expansion, data synthesis, and training on retrieval feedback. But the generative part usually only augments the query. The final matching is still handed off to a retriever further down the line.
CoGR takes a different route. It trains language models to construct the retrieval representations themselves, on both sides: one generator for queries, one for items. Each generator produces a compact set of keywords, and those keywords are matched directly through an inverted index. That keeps the approach compatible with the keyword-based retrieval infrastructure already in place.
Training has two stages. Supervised fine-tuning comes first and establishes a keyword space the two sides share. Then comes co-evolving reinforcement learning. The query generator and the item generator are optimized in turn with GRPO, each against a frozen index built by the other side. While one side learns, the other stays put, so each generator is always aiming at a fixed target. Both chase the same objective, the F one score of retrieving the right items for a query.
The two sides earn that reward differently, because they stand in different places. The query side issues the search, so it receives the retrieval F one score directly. The item side never searches at all. It is only ever found. So it receives a counterfactual marginal reward instead: the change in the query side's F one score that its own generated keywords caused. An item's keywords are credited by how much they help queries find it.
CoGR is compared against ten representative baselines, spanning sparse, dense, and generative retrieval. It achieves the best performance on two datasets. On an internal APP Marketplace dataset, it improves the F one score over the strongest baseline by ten point nine percent. On the public WANDS benchmark, the improvement is thirty-six point one percent. Further analysis shows that the co-evolution is stable, and that the keyword spaces of queries and items grow increasingly aligned as training proceeds.
The title's phrase, it takes two to match, carries the design. Neither side can learn its keywords in isolation, because a match only happens when both choose the same words. Training them in alternation, each against the other's fixed index, and rewarding the item side by its effect on the query side, turns two separate generators into partners converging on a shared vocabulary.
Paper Quest · 7 chapters · about 41 min
Play this paper
Learn it by doing: make the calls the authors made, guess the result before you see it, and defend it in a viva graded on your own words. Chapter 1 is right here.
Chapter 1 🧩 · The problem
Retrieval decides what everything downstream gets to see. Here is a system where usually only half of it learns.
You run retrieval for an app store's search and ads: from a huge pool of items, pick the candidates that ranking and auction will see. An item missed here is lost for good.
The road ahead
- 1 · The problem ~7 min Retrieval picks the few candidates everything later sees, and today language models mostly help the query while the items usually stay fixed.
- 2 · What came before ~3 min
- 3 · The key idea ~9 min Two models write short keyword sets, one for queries and one for items, trained in turn so both sides meet in an inverted index.
- 4 · Choose your own research ~3 min
- 5 · Build the method ~8 min First fine-tune both generators into one keyword space, then train them in turn against a frozen index, then match keywords through an inverted index.
- 6 · The experiment ~6 min You’ll guess: On the public WANDS product-search benchmark, by how much did CoGR improve its retrieval score over the strongest of ten baselines?
- 7 · The viva ~5 min Three questions from the examiners, answered in your own words. Win it for the paper’s trophy.
Free, with Google or an email address. Your stars and progress are kept.