Yue et al. (2025) showed that RLVR-trained models beat their base models at pass@1 but lose at large : the set of problems the model can solve at all shrinks. This paper asks why. Its answer has two parts. Training on some problems actively lowers the likelihood of correct solutions to others (negative interference), and on-policy sampling makes RLVR reinforce whatever the base model already found most likely (winner-take-all). The proposed fix, SELF (Selective Examples with Low-likelihood and Forward-KL), trains only on problems where the greedy answer fails and swaps reverse KL for forward KL.
My short take: the mechanism is plausible and SELF's large- results against GRPO are consistent, but the presentation has errors in most of the key equations, and the diagnostic evidence is weaker than the framing suggests.
Key ideas
- Negative interference. Learning to solve certain training problems actively reduces the likelihood of correct solutions for others, which drives pass@ down.
- Winner-take-all. RLVR disproportionately reinforces problems whose correct solutions already have high likelihood under the base model, while suppressing initially low-likelihood ones.
- Each prompt is its own MDP. Standard RL is effective at learning a single MDP. In LLM reasoning, each problem induces its own MDP with a distinct, unknown reward function , so learning one can hurt another.
- SELF. Selectively trains only on problems with a low likelihood of arriving at correct answers, while preserving previously learned behavior.
Setup
An LLM policy generates autoregressively:
RLVR maximizes a KL-regularized verifiable reward, starting from the base model :
There's no entropy term here, and neither GRPO nor DAPO includes one by default. In their experiments the authors also drop the KL term () and use no entropy loss.
The reward is a per-prompt check:
so the reward function itself changes from prompt to prompt. (The actual training reward is shaped: for a correct boxed answer, for a wrong boxed answer, and otherwise.)
Two framings from related work
Churn. When you update a network on a batch, its outputs also change on inputs that weren't in the batch. That off-batch change is churn. Tang & Berseth (2024) find that plasticity loss correlates with drastic confidence changes of this kind.
Varying prompt-induced objectives. Treat each prompt as a task: it defines its own MDP with its own reward function. Every batch then mixes a different set of objectives, so RLVR training looks like multi-task learning where the tasks change from batch to batch, and improving one task can hurt another. This is a much finer-grained notion of "task" than, for example, ReMind, which treats a single dataset as a task.
Per-step influence
The core tool measures how one update changes the log-likelihood of some other problem–solution pair :
Proposition 3.1. For a sufficiently small learning rate ,
where
The thing that tripped me up at first: the two pairs play different roles.
- is the sample the model is trained on at step : a prompt from the training set and a response sampled from , with advantage . It enters only through the parameter update.
- is any other pair being watched: another training problem, a test problem, or a probe. It enters through the quantity being measured.
Both gradients in are evaluated at , just before the update, and belongs to the same step whose effect is being measured. In practice step uses a whole batch (64 prompts, 8 rollouts each), so the real change is a sum of these terms over the batch.
Derivation
The update comes from :
Step 1: turn it into a function of . Let . Then
Step 2: first-order expansion.
Step 3: substitute back.
The advantage is bounded (finite rewards and group normalization), and assuming the gradient norm is bounded too, the remainder is . That gives Proposition 3.1.
Aside: why the remainder is
The first-order Taylor approximation with an explicit error term:
Solving for the leftover:
So is "whatever is left over": the slope of the secant line from to , minus the slope of the tangent at .
If is twice differentiable, the Lagrange form makes the error explicit:
so , and when is bounded the error is . For a parameter step , the squared distance scales like :
Reading the result
The sign of each term is the sign of , not of alone:
| Training sample | Gradient alignment | Effect on the watched pair |
|---|---|---|
| correct, | aligned, | goes up (positive transfer) |
| correct, | anti-aligned, | goes down (negative interference) |
| incorrect, | anti-aligned, | goes up |
The last row matters: pushing down a wrong answer can raise a correct one.
Measuring interference
A lower bound, not an approximation
is expensive: it needs per-example gradients over billions of parameters, for every pair. With , Proposition 3.1 gives
The paper says this lets the measured change approximate , but it's only a lower bound, and it works in one direction:
- a large observed forces a large , but
- a small does not imply a small , because the change can be small simply because .
Luckily, the valid direction is the one the paper needs: if the change keeps growing, gradient entanglement must be growing too. And the change is cheap to measure (forward passes before and after an update), and it's the quantity pass@ actually depends on.
Further gaps: with a batch update the bound constrains a sum over the batch, not one pair; training likely uses an Adam-style optimizer, so the true kernel is preconditioned rather than a raw dot product; and everything is first-order.
Definition 4.1: interference
With the paper's conditioning typo fixed:
In words: after one training update, how much did the model's log-likelihood of known-correct answers change, on average? That is, how much does an update affect behavior that was already correct.
- is a correct response and an incorrect one. The means "filtered to correct answers," not "positive part."
- is called a behavior policy, but training is still on-policy. only decides where the probe answers come from. The authors use and build the probe set once, from 4 base-model samples per training prompt at temperature . A fixed base-model set asks the right question (does RLVR lose what the base model could do?) and gives a stable yardstick across training.
- The base model never changes. tracks how the trained model's probability of the base model's correct answers moves. Negative means net damage (negative interference); positive means the update helped.
- It's a signed average, so it has a magnitude, but a net one: gains on some pairs and losses on others cancel. The paper calls it the "direction" of influence; more precisely, it's the net sign of advantage-weighted gradient similarity to correct answers.
Written carefully, "sample from " needs a conditioning on correctness, so the precise form is a ratio:
Per-step changes add up (telescope) to the total drift since the start of training:
Influence strength
This is the magnitude of interference per step. It uses all base-model responses, correct or not, and squares the change, so it measures the size of the spillover regardless of direction or correctness. Despite the notation it isn't a norm: there's no square root, so it's a mean squared change.
Plugging in Proposition 3.1, it's roughly times the mean of the squared advantage-weighted kernel, so it's large only when gradients of training examples overlap with gradients of unrelated probe examples. If were diagonal (every problem with its own direction in parameter space), it would be zero.
| Influence strength | ||
|---|---|---|
| Probe responses | correct only | all, correct or not |
| Per-pair change | signed | squared |
| Question it answers | Did the update help or hurt previously correct answers? | How big is the spillover onto other examples? |
Why have both? For the central claim, mostly suffices. The influence strength adds three things:
- It separates "nothing moved" from "things moved and cancelled," since a signed average hides offsetting changes:
- It explains why worsens: rising influence strength shows updates are spilling over more, not just becoming more harmful at the same size.
- It supports the regularization argument (clipping doesn't control out-of-batch effects) and the SELF evaluation.
A caveat the paper glosses over. Nonzero influence strength isn't necessarily harmful. Positive transfer raises it too, and it's how RLVR improves pass@1 on unseen test problems. Zero spillover would mean no generalization at all. So "the model struggles to distinguish problems" is one interpretation of rising influence strength, not something it shows on its own. The paper's claim holds only because it pairs it with .
Caveats on both definitions
- The scale of is ambiguous. Appendix C.2 (Eq. 16) defines as a per-token average, but the perplexity in Eq. (6) divides by again, which only makes sense for a sequence total. The same symbol means two things.
- The probe set is biased toward easier problems. Correct probe answers come from only 4 base-model samples per prompt, so problems with rare correct solutions barely appear, and problems with several correct samples count several times. mostly tracks interference on problems the base model already solves fairly often, not the rare-solution problems that matter most for large .
Experimental setup
- Models: Qwen2.5-Math-1.5B and 7B, Llama-3.2-3B-Instruct.
- Training data: DeepScaleR, about 40k math problems.
- Benchmarks: AIME24, AIME25, Math500, Minerva.
- Training: VERL, GRPO, learning rate , batch of 64 prompts with 8 rollouts each, temperature , 500 steps, no reverse KL and no entropy loss.
- Evaluation: temperature , top-p .
What the dynamics show (Fig. 2)
Averaged over the four benchmarks (Qwen2.5-Math-1.5B, going by Fig. 10):
- (A) Pass@1 rises steadily, while Pass@256 peaks around step 200 and then falls. The model gets sharper but narrower.
- (B) Influence strength roughly doubles over training (about to ). Each update spills over more onto problems it wasn't trained on.
- (C) starts near zero and drifts down to about . Early updates are roughly neutral for previously correct answers; later ones do more net damage.
- (D) The log-likelihood of the base model's correct answers falls from about to : the accumulated result of (C).
Together: updates increasingly bleed onto other problems, the bleed increasingly hurts correct answers, and those answers lose probability over time. Larger models suffer more. In Fig. 10, reaches roughly for the 7B model and roughly for Llama.
Things to be careful about in panel (A):
- The axes are heavily zoomed. Pass@256 goes from about to , a drop of roughly 0.3 points. The dual axes make it look like a dramatic crossover.
- The x-axis starts at step 150, so the base model's value isn't shown.
- Single run, no error bars. A shift of a few tenths of a point could be within run-to-run variance.
Also, the magnitudes in (C) and (D) don't reconcile. If each step moved per-token log-likelihood by around on average, 500 steps would lower it by around , yet (D) falls by only a few hundredths. The sign and trend are the reliable part; the absolute scale likely reflects some unstated averaging or normalization.
Does interference predict pass@k? (Fig. 3)
The setup: pick pairs of checkpoints and with later, compute between them on correct test-set answers (with the earlier checkpoint as ), compute the change in Pass@128, and correlate the two across many pairs. Each dot is one checkpoint pair. The fitted line slopes upward on every benchmark, with Pearson to .
The claim is that interference is an indicator of pass@ decrease. AIME24 and AIME25 don't support that claim. The reference for "did coverage shrink?" is the horizontal line at zero, not the fitted line:
- AIME25: almost every dot has negative , yet most have positive Pass@128. Even the fitted line stays above zero across nearly the whole range. Negative interference mostly coexists with coverage gains.
- AIME24: mixed; plenty of dots show negative interference together with a Pass@k increase.
- Math500: every dot has strongly negative (between and ), yet many pairs gained coverage. All changes are under 1 point with Pass@128 near its ceiling of about 95%, so this panel is close to noise.
- Minerva: the one panel that fits the story. Most dots are below zero and the fitted line is negative throughout.
It also doesn't look like a clean linear relationship: on the left, many dots sit above the fitted line. Least squares balances squared distances, not counts, so a few far-below dots can pull the line down. The slope may be driven by a handful of extreme pairs; a rank correlation would be more robust, and the paper doesn't report one.
More issues:
- Training time may drive both axes. Both quantities trend with training steps, and pairs further apart in time have larger changes on both. The pairs also share checkpoints, so the dots aren't independent.
- Part of the link is built in. Both axes use the same test problems, and lowering the probability of correct answers mechanically lowers the chance of sampling one in 128 tries.
- The AIME sets are tiny (30 problems each), so a few points of Pass@128 is roughly one problem flipping.
- may be below the crossover on AIME. For the 1.5B model, GRPO beats the base at (8.50 vs 4.45 on AIME25) but loses at (64.05 vs 67.80). If the crossover lies above 128, Pass@128 can keep rising while coverage at larger shrinks.
- The scale differs from Fig. 2(C) by a factor of hundreds, consistent with cumulative multi-step changes, but unexplained. This is also a different quantity from Definition 4.1, which is per-step.
What the figure actually supports is a relative claim: pairs with more negative interference tend to do worse on Pass@128 than pairs with less. Negative often accompanies Pass@k gains, probably because the model also learns new correct solutions while losing old ones, and only sees the losses.
Why: on-policy sampling and winner-take-all
Perplexity as a probe
Two models play different roles: (the subscript) writes the responses, and (the argument) scores them. Per response, perplexity is one over the geometric-mean probability assigns to each token:
Perplexity means predicts every token with certainty; means a coin flip at every token. The paper's values of about to mean an average per-token probability of roughly down to . Lower means " finds these responses natural."
Fig. 4 swaps who writes and who scores:
| Panel | Written by | Scored by | Trend | Meaning |
|---|---|---|---|---|
| Left | RL model | base model | falls | RL outputs look increasingly typical to the base model: it's moving into the base model's highest-likelihood regions, not somewhere new. |
| Middle | base model | RL model | rises | The RL model finds the base model's outputs increasingly unlikely, and correct ones even more so: it's dropping the base model's diversity. |
| Right | base model | base model | improved problems lower | Problems RLVR improved were ones where the base model was already confident; problems it hurt were ones where it was less confident. |
So RLVR sharpens the base model toward its own most confident outputs. That helps where those outputs were correct, and hurts where the correct answer was in a lower-likelihood region.
Caveats: the right panel's boxes overlap heavily (medians of roughly vs ); perplexity near 1 is dominated by easy tokens (formatting, restating the problem), which can hide what happens at the few tokens where reasoning branches; and small per-token shifts compound, so the middle panel's rise from about to is a very large drop in whole-response probability over roughly 1,000 tokens.
What "sharpening" does to one prompt
The shift is about responses, not prompts. The model becomes more confident in a narrower set of answers, and less confident in the alternatives the base model used to produce, correct or not. Two illustrative prompts (made-up numbers):
The base model's favorite answer is correct:
| Solution | Correct? | Base model | After RLVR |
|---|---|---|---|
| A | yes | 50% | 90% |
| B | yes | 20% | 3% |
| C | no | 30% | 7% |
Accuracy goes up. But the second correct solution B has almost vanished.
The base model's favorite answer is wrong:
| Solution | Correct? | Base model | After RLVR |
|---|---|---|---|
| A | no | 60% | 90% |
| B | yes | 10% | 2% |
| C | no | 30% | 8% |
The model is now very confident in a wrong answer, and the only correct solution is so rare it may never be sampled even with many tries. This is how pass@ at large shrinks.
The on-policy gradient (Fig. 5)
The REINFORCE gradient for an action :
The update is scaled by the response's current probability. In Fig. 5, each panel is a cartoon distribution over responses (x-axis squashed to one dimension), gray before an update and blue after, with red arrows showing how much each marked response moves:
- Left: a rare correct answer barely moves. sits in the tail, so rewarding it barely changes the distribution. It's almost never sampled, so it's almost never learned from.
- Middle: the rich get richer. With two correct answers, the one that started more likely gets a much bigger boost. Repeat over many steps and the other fades.
- Right: punishing a wrong answer mostly helps the favorite. (a sampled wrong answer) is pushed down. Under a softmax, each other response's logit rises in proportion to its current probability, so most of the freed mass flows to , the greedy answer, and only a little reaches the correct but rare . can be right or wrong; if it's wrong, you've moved probability from one wrong answer to another. This is the squeezing effect from Ren & Sutherland (2025).
- Never sampled means no signal. If no rollout is correct, every advantage is zero and nothing is learned.
One caveat: in this equation, the factor is exactly how often gets sampled. On the rare occasions a low-probability correct answer is sampled, its per-sample update isn't smaller, so "small updates" and "rarely sampled" are the same effect counted twice. In GRPO a rare success can even get a larger push: with binary rewards, if 1 of 8 rollouts is correct, group normalization gives it an advantage of about . The left panel is more accurate for plain REINFORCE than for GRPO, though a correct answer that's never sampled still gets nothing.
Isn't sharpening a good thing?
Partly. It's exactly what raises pass@1. But the mechanism decides who gets richer by probability, not correctness, so it's only good when the favorite answer is right. The paper treats it as a problem for three reasons:
- Coverage shrinks. When the favorite is wrong, the correct answer drops below what even 256 or 1,024 samples will find.
- It spreads across prompts. Fig. 5 alone is per-prompt dynamics. With shared parameters, a strategy reinforced on training problems gets pushed onto other problems too, including ones where it's the wrong strategy.
- It limits future learning. RL can only reinforce what it samples. Once alternative solutions vanish, later training can't discover they were better.
If you deploy with a single greedy answer, sharpening is mostly a win. If you rely on many samples, best-of- with a verifier, or further RL, the lost diversity is a real cost.
Case study: code vs. language reasoning
Qwen2.5-Math has two reasoning modes: code-based and natural language. During RLVR, code reasoning steadily disappears and language reasoning takes over, because language reasoning had better initial accuracy on the training set. On Minerva, where code reasoning worked better for the base model, performance drops. This is the most convincing illustration in the paper of winner-take-all spreading across prompts.
Why standard regularizers don't help
- Clipping only constrains probability ratios on the training batch. Trust-region violations stay flat on the batch but grow steadily on the probe set (Fig. 7), so clipping doesn't control the out-of-batch damage.
- Reverse KL is mode-seeking. It barely penalizes dropping probability where the policy puts low mass, and it tends to favor collapsing onto the base model's high-likelihood mode.
SELF
The idea: stop letting the easy problems dominate training, and penalize forgetting what the base model could do. At each step:
- Filter. For every prompt in the batch, generate one greedy answer . If it's already correct, skip the prompt for this update.
- Train on what's left. Run ordinary GRPO on the kept prompts.
- Don't forget. Add a small forward-KL term toward the base model, which acts like light supervised training on base-model outputs. Unlike reverse KL, it penalizes dropping probability on anything the base model produces. The weight is tiny: .
The paper's Eq. (9), as printed:
This says the opposite of the text: read as "the greedy answer is correct," it keeps only the easy problems. It also puts a reward value inside a set of completions, which doesn't type-check. What they mean:
If the greedy answer is wrong, the prompt gets a normal GRPO update; if it's right, the reward term vanishes. The KL term applies to every prompt. Note that is never trained on: it's only a test for whether to keep the prompt, and the update comes from the sampled answers .
Results
Training dynamics (Fig. 8): SELF's training accuracy is much lower, as expected since it only trains on problems it's failing. By the paper's own metrics it's healthier: higher entropy, less negative , smaller influence strength, and fewer trust-region violations.
Selected numbers from Table 1:
| Setting | Base | GRPO | SELF |
|---|---|---|---|
| Qwen-7B, AIME25, Pass@1024 | 67.57 | 58.60 | 72.0 |
| Qwen-1.5B, AIME24, Pass@1024 | 75.86 | 67.77 | 80.94 |
| Llama-3B, Minerva, Pass@256 | 49.26 | 50.73 | 57.35 |
| Qwen-1.5B, Minerva, Pass@256 | 70.67 | 65.07 | 68.75 |
Counting across all 12 model–benchmark cells:
- At the largest , SELF beats GRPO in 12 of 12 and beats the base model in 9 of 12.
- At pass@1, SELF is slightly below GRPO in 7 of 12, so there's a small cost.
The extra greedy generation is roughly offset by training on fewer prompts, so overall compute is about the same as GRPO (Appendix G).
What's missing
- No ablation. SELF changes two things, and they're never tested separately. With , the forward-KL term may contribute little.
- No comparison to similar filtering. DAPO (Yu et al., 2025), which the paper cites, already drops prompts where all rollouts are correct. SELF's filter is stricter but never compared against it.
- Single runs, no error bars, while several Table 1 differences are a point or two.
- W-REINFORCE (Zhu et al., 2025), the other diversity-oriented baseline, only appears in an appendix as training curves (it collapses after about 300 steps), not in the results table.
Errata I noticed
- Eq. (5) and the influence-strength definition: the response should be sampled from , not . The same typo appears in the text after Definition 4.1.
- "Sampling from " needs an explicit conditioning on correctness (see the ratio form above).
- Influence strength is written as a norm but is a mean of squares.
- Eq. (9): the indicator is flipped and mixes types.
- Appendix C.1, Eq. (13): expands where it should be , which makes the two pairs look identical.
- Proposition C.1: writes ; the last argument should be .
- normalization: per-token in Eq. (16), but Eq. (6) divides by again.
- Appendix F cites Fig. 2 for W-REINFORCE; it should be Fig. 12. Appendix D refers to "section 2" for the MLE result, which should point to D.1.
- Section 4.2: "negative inference" should be "negative interference."
My take
It's an arXiv v1, and it reads like one: errors in nearly every key equation, and diagnostic evidence that is inconsistent in places. The Fig. 3 correlation doesn't support the "pass@ decrease" framing on AIME, the Pass@256 drop in Fig. 2 is about 0.3 points on a zoomed axis, the magnitudes in Figs. 2(C) and 2(D) don't reconcile, and the probe set over-represents problems the base model already solves. The theory is mostly a standard first-order learning-dynamics argument (following Ren & Sutherland, 2025), with a one-directional bound and a bandit analysis that ignores GRPO's advantage normalization.
What holds up: the mechanism (on-policy sampling plus softmax squeezing sharpening the base model's favorites) is plausible and fits related work; the code-to-language collapse on Minerva is a concrete illustration; and SELF beats GRPO at large in every cell of Table 1, sometimes by a lot.
How I'd cite it: as a proposed mechanism for RLVR's coverage shrinkage, plus a simple intervention with promising large- results. The diagnostic measurements (, influence strength, the Fig. 3 correlation) are suggestive rather than conclusive, and the method lacks ablations and variance estimates.