When similar problems
teach the wrong lessons.
First surfaced in Tandemly Briefing — 2026-06-11.
A team at Rice University trained a retriever to find not the most similar math problems, but the most useful ones. Not "what looks like this problem?" but "what would teach someone how to solve this problem?" The distinction, it turns out, matters a lot.
Semantic similarity is
not reasoning similarity.
Retrieval-augmented generation has a subtle flaw when used to supply training demonstrations for reasoning tasks. The way most retrieval systems choose examples is wrong for what these tasks actually need.
When you train a language model to reason better, one approach is to give it examples of other problems solved correctly. The model can observe the reasoning strategy in those examples and apply something similar to the target problem. This works well when the retrieved examples are genuinely analogous: same kind of reasoning, same structural move, similar mathematical machinery.
The catch is in how "similar" is defined. Standard retrieval systems, including the embedding-based ones that power most RAG pipelines, measure similarity in terms of topic and surface-level language. A problem about combinatorics retrieves other combinatorics problems. A problem involving quadratic equations retrieves other quadratic equations.
But the reasoning strategy that cracks a particular combinatorics problem might be a modular arithmetic trick that looks nothing like the retrieved examples. Meanwhile, a problem from a completely different domain might share the exact same structural approach. Surface similarity and reasoning similarity are not the same thing, and conflating them means you're feeding the model the wrong teachers.
What if the retriever was trained specifically to surface examples whose solution paths are useful for the target problem, rather than examples that look like the target problem? And what does that do for reinforcement fine-tuning on hard math?
Three stages,
one key shift.
The RA-RFT framework (Retrieval-Augmented Reinforcement Fine-Tuning) makes retrieval aware of reasoning utility. It does this across three stages, each building on the last.
The retrieval corpus is OpenR1-Math-220K, derived from NuminaMath-1.5: AoPS Forum problems, AMC/AIME 1984 through 2023, MATH, and olympiad problems. Importantly, all of this source material predates the evaluation benchmarks, so there is no contamination of the kind that can inflate results in math benchmarks.
Gold-relevance distillation is the enabling step. Labeling every pair of math problems by reasoning utility manually would be prohibitively expensive. Using a capable judge model to generate those labels at scale makes the approach practical. The distillation turns the retriever training problem into a standard contrastive learning task: bring reasoning-analogous pairs together in embedding space, push non-analogous pairs apart.
Up to 7.1 points
on AIME 2025.
RA-RFT was evaluated on four competition-level math benchmarks against GRPO (the standard reinforcement fine-tuning baseline). Results were measured using avg@32: the average score over 32 sampled solutions at temperature 1.0.
On AIME 2025, RA-RFT outperformed GRPO by 7.1 percentage points on Qwen3-1.7B and by 2.8 points on Qwen3-4B. Averaged across all four competition benchmarks, the gains were 4.1 points (1.7B) and 2.6 points (4B). These are meaningful improvements on benchmarks where frontier models struggle to exceed 50% accuracy, and where any gain reflects genuine reasoning improvement rather than scale alone.
The authors argue that reasoning-aware retrieval is orthogonal to reward design and curriculum: the retrieval improvement and the RL training objective are independent axes. This means RA-RFT gains can be stacked on top of other RLVR improvements without interference. If your team has been working on better reward shaping or smarter curricula for reasoning models, the retrieval component is an additive lever, not a replacement for what you've already built.
Both the 1.7B and 4B variants of Qwen3 showed gains, which the authors take as evidence that the benefit comes from the retrieval structure rather than from properties specific to one model scale. The absolute gains are larger at 1.7B, which fits a consistent pattern in reasoning research: smaller models have more room to improve from better training signal.
The evaluation is limited to competition-level mathematical reasoning with verifiable rewards. Whether the approach generalizes to other domains where "reasoning utility" is harder to define and where no clear correctness signal exists remains an open question. The judge-model distillation step requires a capable model to generate reliable relevance labels. The approach is also a training-time technique: the retrieval investment occurs at training, not at inference, so it does not directly reduce inference costs.
What this means
for builders.
RA-RFT targets a specific part of the training pipeline: which examples you retrieve to help a model learn. The implications are most direct for teams building and fine-tuning reasoning models, but the underlying principle about retrieval for training is broader.
Where to go
from here.
Concrete next steps if you want to go deeper or try this approach on your own tasks.