AI agents are increasingly trusted with long, open-ended work. They fix bugs across large repositories, operate terminals for hours, and chain numerous tool calls toward a single goal. The strongest models now solve a meaningful share of such tasks, yet on the hardest ones failure is still the common outcome, and closing that gap is one of the central problems in post-training.
The standard recipe is reinforcement learning against a verifier. The agent attempts a task many times, an automatic checker scores each attempt, and the model is pushed toward the attempts that scored best. When success is rare, this recipe runs into a basic problem. If the checker reports only whether the task was fully solved, almost every attempt on a hard task scores zero, and a group of identical zeros teaches nothing. The natural remedy is partial credit, scoring each attempt by the fraction of requirements it met, and it is a common choice in practice.
Used naively, partial credit can work against the very goal it is meant to serve. Even though it is built from the same checks that define success, a model trained on it can learn to satisfy the easy checks while giving up on the route that satisfies them all. Blending partial credit with the pass/fail signal does not solve this, since a failed attempt can still be reinforced right alongside a successful one unless almost all of the weight sits on pass/fail. We introduce binary-gated GRPO, which removes this conflict while keeping what partial credit has to offer. Whether partial credit then helps or hurts completion comes down to a single quantity that the scores alone cannot reveal. The good news is that with binary-gated GRPO, harm requires a specific combination of conditions, and in a natural setting partial credit can only help.
The verifier rarely grades a single final answer. More often, it checks many conditions once the attempt is over. A coding agent may face a test suite. A tool-use agent may face a checklist. A rubric may be decomposed into atomic, pre-specified requirements. In each case, we assume deployment cares only whether the agent satisfied every required condition.
That all-pass objective is the right one. It is also an aggressively lossy summary of what the verifier observed.
Suppose a verifier evaluates binary checks. Let record whether check passes, let positive weights sum to one, and define
Here is the binary all-pass return and is the terminal fractional return, which makes the partial credit described above precise. Because every weight is positive, . The fractional return therefore retains the all-pass outcome and can preserve variation among failures.
This is why fractional return is compelling. It is derived directly from the atomic conditions whose conjunction defines success, although the weights still choose how to compare non-all-pass outcomes. The full check vector says which requirements a rollout met, while the scalar records only the weighted fraction.
and are returns, not rewards. In reinforcement learning, a reward is defined for a single transition, one action taken in one state. The verifier instead scores the finished trajectory as a whole, and a score of the whole trajectory is, by definition, a return. Calling such scores rewards is common, but it is a textbook mistake. We therefore refer to both as returns throughout.
We study the tension raised at the start for GRPO (Shao et al., 2024), a standard method for this kind of training. The question is not whether fractional return carries extra information, since it does, but whether GRPO can use it without trading completion for a more attractive form of failure.
GRPO samples a group of rollouts for each prompt and labels each rollout by how its return compares with the rest of its group. Two different things can go wrong. The first happens inside a single group. Fractional return can order trajectories differently from completion, and after centering, that disagreement can give a failed rollout a positive label, reinforcing it even when a successful rollout sits in the same group. The second is subtler and happens across groups. The same prompt yields a mixed group, containing both successes and failures, on one draw and an all-fail group on the next, and a rule that switches to fractional return only on all-fail groups changes what training optimizes, even when every single group looks fine.
In this post, we first make both sides of that tension precise. We then show that mixing fractional return with binary return does not remove the within-group conflict, and introduce binary-gated GRPO, which does. Next, we derive exactly what the cross-group problem does to training, identify the single quantity that decides its direction, and show that it is harmful only under specific conditions. We close with a practical rule for real training runs. Proofs of every proposition are collected in the appendix.
We work with fractional return throughout because it lets every claim be stated exactly. The central results do not depend on its particular form, however. Binary gating, what the all-fail fallback optimizes, and the quantity that decides whether it helps all apply unchanged to any score assigned to a whole trajectory, such as a sum of per-turn scores.
Why fractional return is tempting
Binary completion collapses every failure to the same label. A trajectory that passes nine of ten checks and a trajectory that makes no progress both receive . That is appropriate as the deployment objective, but it discards information that may be predictive of how to reach completion.
Let denote one policy decision, comprising the full context available immediately before a sampled agent token together with that token. All expectations in this section are under one joint distribution of the decision and the trajectory that contains it. Define the centered completion-value target at that decision,
and the part of terminal fractional return that remains after pass/fail is known,
For this nondegenerate discussion, assume both success and failure have positive probability. On successful trajectories . On failures, it records whether a rollout achieved more or less fractional return than the average failure. These definitions let us state the information claim precisely.
Proposition 1.What fractional return adds.
For any square-integrable target that depends only on pass/fail, and any scalar ,
For a fixed binary-only target , if
then some positive coefficient improves that target. In particular, let be the best binary-only target. Whenever , the target is strictly more accurate than every binary-only target, with optimal coefficient
Proposition 1 is an information result, not a guarantee for a particular policy-gradient estimator. It says that fractional return can carry information about the completion value of intermediate decisions that pass/fail labels alone cannot represent, and it identifies when that information improves prediction of that value. It does not say that pushing the policy toward higher fractional return helps completion. Carrying information and pointing an update in the right direction are different properties, and the rest of this post is about the gap between them.


Now make the GRPO setup precise. For one prompt, sample a group of independent rollouts. For a scalar return of rollout , the centered label is
Throughout, GRPO means this raw centered label applied to the log-probability summed over each trajectory. A leave-one-out baseline gives the same label up to a factor of . The original GRPO also divides each group by its standard deviation and averages token losses within each sequence. A later section says which results survive those choices. We call the rule binary GRPO.
With binary all-pass return, every all-fail group has . Its return-derived task gradient is therefore exactly zero. On hard tasks, these groups can be common rather than exceptional, and a difficult prompt contributes no task gradient of its own until a rollout happens to complete.
Something has to fill that silence. Larger groups, curricula, demonstrations, and learned process reward models can all help, but each costs more or brings its own assumptions. Fractional return is the cheapest candidate, because the verifier already computes it.
The simplest options are to train directly on , or to add beside . Both are tempting, and both deserve a closer look.
Fractional return can silently prefer failure
The attraction of fractional return makes the following failure easy to miss. The score is built from the conditions that define success, yet it can still induce a direct preference for a trajectory that never completes the task.
Consider a terminal task with five equally weighted checks. Under policy , half the rollouts pass three checks and half pass two. Thus
Under policy , an implementation that preserves every required behavior completes all five checks with probability , while the other rollouts pass none. Thus
Fractional return prefers , the policy that never finishes the task. Binary completion prefers . Group centering does not change this. For independent rollouts, the expected GRPO update on is exactly times the gradient of (Appendix A.4), so GRPO trained on inherits this preference.


This is not a pathology caused by using an imprecise evaluator. Both returns came from the same checks. The problem is that satisfying many checks can be easier than preserving the route that satisfies all of them. For example, an agent can implement visible new behavior while breaking a legacy invocation that is required for full completion.
The literature would call this reward hacking, even though the quantity being gamed here is a return. The example supports a sharper claim, and a more useful one. Even though fractional return is computed from the very same checks that define success, it can still rank a shortcut above completion.
Mixing still reinforces failure
One might be tempted to retain binary completion and naively mix it with fractional return,
While this appears conservative when is large, it turns out to be far from conservative in the rare-success regime.
Consider rollouts. One completes, one failure obtains , and the remaining fourteen failures obtain . The group means are and , so with the failure receives
It receives a positive label despite a successful rollout in the same group. In the raw score-function term, a positive label pushes the failed rollout’s sampled actions toward higher probability. The group has already demonstrated completion, yet the mixture still reinforces a failure direction. We call a positive label on a failure in a mixed group a sign reversal.
This is not a peculiarity of the seventy-percent example. A sign reversal can occur in any mixed group, and the next result gives the exact condition.
Proposition 2.The sharp limit of naive mixing.
In a mixed group with successful rollouts, a failed rollout receives a positive mixed label exactly when
where is the mean fractional return of the other rollouts.
In the example above, , so the failure is reinforced for every . Other verifiers can do worse. Every success scores , which pulls up, but a failure can come arbitrarily close to while its other failed peers score zero. As a result, no choice
is safe for every verifier. With and one success, the binary coefficient must be at least to rule out every such reversal. A specific verifier sets a slightly lower bar. If its failures can score anywhere from 0 up to , the threshold is . With five equal checks, , and for the same group size and one success the threshold is . The criterion cannot fire at all when a group has a single failure, because that failure sits below peers that all have .
A binary weight close enough to one does prevent the reversal. The trouble is where that weight is needed. When a group contains many successes, a modest weight suffices. When successes are rare, which is exactly the regime where fractional return was supposed to help, most mixed groups contain a single success, and the weight needed to rule out every reversal is , already at . A weight that large leaves fractional return only a minor role. Mixing is safe exactly where it is unnecessary, and unsafe exactly where it is tempting.
Let completion decide first
Every fixed mixture sets an exchange rate between fractional return and completion, while the deployment criterion gives completion strict priority. An exchange rate is the wrong kind of object. We propose a composition that expresses the priority directly, which we call binary-gated GRPO. It lets completion decide wherever it can, and admits fractional return only where completion is silent.
Let be the number of successful rollouts in the group. The binary-gated terminal label is
In a mixed group, completion already ranks every success above every failure. It does not rank failures against each other, and the binary-gated rule deliberately gives up that information, so that fractional return can never turn a failure into a positive example. In an all-fail group, binary completion ties every rollout, so fractional return is admitted as a tie-breaker. We call this all-fail branch the fallback. In an all-pass group, every rollout has , so both returns are constant and the group is silent.
Proposition 3.Binary-gated labels separate successes from failures by sign.
In every mixed group, binary-gated GRPO assigns a strictly positive label to every successful rollout and a strictly negative label to every failed rollout.
This removes the reversal that mixing allowed. A high-scoring failure can no longer receive a positive label in a group that already contains a completion.


What it does not control is what happens across groups. A high-scoring failure in an all-fail group still receives a positive label, while successes in other groups receive theirs, and no single group contains both. The next section shows that, on average, the steps these groups produce can lower completion, and a later section shows when that actually happens.
The all-fail switch changes what the update estimates
Each training step on a prompt draws one group from the current model, and whether that group is mixed or all-fail is a matter of chance. On a mixed draw, binary-gated GRPO steps along completion. On an all-fail draw, it steps along fractional return instead. Each step is sensible on its own, but every step starts from the model the previous one produced, so their effects on completion add up, and an all-fail step can undo part of what a mixed step gained.
It is tempting to call the all-fail branch “centered fractional return” and to treat the group mean as a harmless baseline. Applied to every group, centering is indeed a baseline, since in expectation it only rescales the gradient of the expected return. The all-fail branch is not applied to every group. It is applied only after every rollout has failed, and that selection changes what the fallback optimizes.
Write
Here is the probability that a single rollout completes. For independent rollouts, , the th power of , is the probability that all rollouts in a group fail.
Let be the trajectory score function for rollout , namely the sum of log-policy gradients over its policy-controlled actions, and write for the score of a single generic rollout. Every gradient is taken with respect to the policy parameters. Everything here refers to a single fixed prompt. Assume independent on-policy rollouts, , and a verifier with no explicit parameter dependence. The results below concern the expected raw return-derived score estimator for one step, before clipping, group-standard-deviation normalization, or other optimizer transformations.
The expectation below is over the group drawn at a single step from the current model. It is the average step, with mixed and all-fail draws weighted by how often they occur, and its projection onto says whether a step taken from the current model raises completion on average, to first order in the step size.
Proposition 4.The all-fail fallback follows conditional fractional return.
For the binary-gated estimator
we have
The first term comes from mixed groups and is the intended completion gradient. The second comes from all-fail groups, which occur with probability , and follows the mean fractional return among failures. It is not the gradient of all-pass completion, and it need not point in the same direction. When the two conflict, no single step reveals it, because each step contributes to only one of the two terms.
Proposition 4 also clarifies what binary-gated GRPO buys in expectation. No single group trades completion for fractional return, but averaged over draws, the two directions still combine, with weight on relative to . In expectation, this acts as an effective exchange rate, although it is never applied inside a group. The naive mixture, by contrast, applies a fixed exchange rate inside every group. It is ordinary centering of , so its expected update is (Appendix A.4)
Two differences favor the binary-gated rule. Its weight on decays geometrically as successes become common, like rather than , and it pays no penalty on the completion term. But when successes are rare enough that , both and are close to one, and the weight each rule puts on is set mainly by its coefficient, or . What binary-gated GRPO still guarantees in that regime is a property of every sampled group, namely that no failure is reinforced next to a success. In expectation, the direction is still there, and its sign is what matters.
Here is a minimal example. Let a one-dimensional policy parameter and a constant produce three terminal outcomes.
| Outcome | Probability | ||
|---|---|---|---|
| Completion | 1 | 1 | |
| Half-return failure | 0 | ||
| Zero-return failure | 0 | 0 |
One way to read it is as a sequence of choices. The policy first attempts the route that keeps completion possible and completes with probability . Otherwise it commits to the zero-return failure with probability or to the half-return failure with probability . Then
Increasing increases completion but decreases fractional return among failures. Since , and , Proposition 4 gives the expected binary-gated update
For every positive , a sufficiently small makes this a descent direction for completion. The fallback is not malicious. It is faithfully increasing conditional fractional return, which happens to prefer retaining the half-return failure mode.


When fractional return is safe, and when it actually helps
The previous section does not say that fractional return is usually harmful. It says that its direction must be checked.
Assume , and let
The vector is the mean score of successful rollouts, so it points along what the policy does when it completes. The vector points along what distinguishes high-return failures from the average failure, and it equals (Appendix A.4). So asks whether moving the policy toward better-scoring failures also moves it toward completion. If every failure receives the same fractional return, . Unlike any statistic of the returns, is a statement about policy-gradient geometry, and we will see that identical returns can come with either sign.
Proposition 5.Completion-direction contribution of the fallback.
The expected binary-gated update satisfies
The left side is the projection of the expected update onto , normalized so that binary GRPO, whose expected update is , scores exactly . For , two things follow.
- The binary-gated update makes more first-order completion progress than binary GRPO exactly when , and less exactly when . When , its projection onto matches binary GRPO’s, although the updates themselves can still differ.
- The binary-gated update is still an ascent direction for completion exactly when .
These are different statements. “Still ascends” is not the same as “helps more than binary.” In the three-outcome example, the parameter is one-dimensional and . The fallback therefore always pulls against completion there, and for small it overwhelms the completion term.
Proposition 5 also shows why has to be measured rather than guessed. Consider a policy that chooses among three strategies through a softmax over three logits, with probabilities 0.02, 0.49 and 0.49. The first strategy completes with probability 0.9 and otherwise ends in a near miss that scores 0.983. The second never completes and always ends in that near miss, and the third never completes and scores 0. This gives and . Now write the th logit as for a fixed positive constant , and take gradients with respect to . Choosing each so that equals the original logit leaves every probability, and hence every statistic of the returns, unchanged, but the gradients change. The table reports and the completion progress of Proposition 5 for and , and Appendix A.7 gives the formulas behind it.
| Logit scaling | Completion progress | Compared with binary GRPO | |
|---|---|---|---|
| (1, 1, 1) | +0.001 | +1.02 | about the same |
| (1, 0.3, 1) | +0.091 | +3.17 | helps more |
| (1, 1, 3) | +0.287 | +7.89 | helps much more |
| (1, 2, 1) | −0.166 | −2.98 | lowers completion |
| (1, 5, 1) | −0.399 | −8.59 | lowers completion |
Nothing a practitioner can see in the returns distinguishes these rows, yet the fallback ranges from nearly eight times binary GRPO’s progress to pushing completion down. This dependence on parameterization is not a flaw in the criterion. Gradient updates are applied in whatever coordinates the optimizer uses, so their direction genuinely changes with the parameterization. It does mean that has to be measured in the model’s own coordinates rather than predicted from a toy model.
The factor is how often the fallback fires, divided by how much completion signal there is to compete with. Rare success amplifies the effect, and the sign of sets its direction. The same alignment enters the fixed mixture, whose normalized completion progress is , but because of the term it beats binary GRPO only when , a stricter condition than .
This gives a concrete meaning to using fractional return correctly. It does not mean simply adding it after all failures. It means operating the fallback where is nonnegative, and turning it down or off where it is not.
Proposition 6.A benign competence regime.
Suppose checks pass independently with probabilities , and gives each check equal weight. Then, for every ,
Under any differentiable parameterization in which every check probability is nondecreasing in every parameter,
with strict inequality wherever . Equivalently, wherever it is defined.
Thus, in this regime, the terminal fractional fallback never reduces the expected completion-direction progress relative to binary GRPO, and whenever and it strictly adds to it.
This is the positive case worth remembering. If fractional return reflects independent pieces of competence, higher fractional return among failures and more completion are compatible goals. The model is illustrative, and it makes no claim about arbitrary neural-network parameterizations. Within it, difficulty amplifies the fallback’s effect through , but never sets its sign.
What can make negative is structure beyond difficulty. Competing strategies are one source. A shortcut can satisfy many visible checks while making a remaining requirement unreachable, as in the three-outcome example. Unequal weights are another, even when checks are independent. Improving a low-weight check raises , but it also removes high-scoring near-misses from the failure set while adding little fractional return, and that can lower . With weights and and pass rates and , improving the second check does exactly that.


How serious is the cross-group problem?
The two problems differ in kind. The sign reversal of mixing is visible in individual groups. In the rare-success regime, most mixed groups contain a single success, and a high-scoring failure in such a group can be reinforced unless the binary weight is close to one. In the sixteen-rollout example, a 70% weight is not enough. The cross-group problem, by contrast, exists only in expectation, and it needs several conditions at once to do serious damage.
First, success must be rare. The fallback fires only on all-fail groups, which occur with probability . At and , that is one group in 256, and the rule is nearly inert.
Second, the alignment must be adverse enough. By Proposition 5, the update lowers completion only when , not merely when . Difficulty alone never makes negative, which Proposition 6 proves for independent, equally weighted checks. It takes additional structure, such as competing strategies or unequal weights.
Third, the prompt must learn mostly from its own groups. Parameters are shared, so a prompt’s completion can rise through updates driven by other prompts. Suppose prompts share the parameters, write , and for the quantities of prompt , and let the update average the prompts’ binary-gated updates. By Proposition 4, the expected update is
and prompt gains completion at first order exactly when . Prompt ’s own fallback term, which carries the whole single-prompt failure mode, is one of terms in this sum. The other prompts contribute , their completion pressure on prompt , and , their fallback pressure on it. If the other prompts are unrelated to prompt , so that both inner products vanish, the criterion is exactly the single-prompt one, however large is. If they are related, their terms add up across the other prompts while the own term remains a single term, so in a large corpus it is the relations between prompts, not prompt ’s own geometry, that decide whether the fallback helps it.
Fourth, the damage accumulates with repetition. The direction of each step does not depend on how often a prompt is visited, but the distance traveled along grows with the number of visits. A prompt visited times sees rollouts in total, so a prompt whose completion rate is well below will most likely never complete during the run. Its entire contribution is then the fallback term, with no completion term to anchor it.
Put together, the unfavorable corner is a small set of loosely related, rarely solved prompts whose fallback pulls against completion, trained for many epochs, while a large corpus of related tasks traversed a few times sits at the opposite corner. Binary-gated GRPO does not remove the cross-group problem, but the damage it can do is concentrated in the unfavorable corner.
None of this rules the problem out. The protection from related prompts depends on their fallback pressure on prompt , and when those prompts are hard it is fragile. Their completion gradients are small, since , where is the mean score of prompt ’s successful rollouts, while their need not be. A slight adverse alignment between and can then outweigh all of the completion transfer, and these cross-prompt alignments have not yet been measured on real training runs.
What this analysis covers
Propositions 4 to 6 describe the expected update of the raw centered estimator for a single on-policy step. Common implementation choices change that in different ways.
- Group standard-deviation normalization. Dividing a group’s labels by a single positive number preserves every within-group sign, so Proposition 3 and the sign-reversal criterion for a mixed label survive. The expected-update results do not. Each all-fail group is divided by its own standard deviation, which varies with the group’s composition, so the all-fail branch no longer follows , and the sign of its projection onto can differ from the raw estimator’s.
- Per-sequence length normalization. Averaging token losses within each sequence replaces the trajectory score by a length-weighted score, so the centering identity behind Proposition 4 no longer holds exactly. Varying lengths change the size of the update, and when length correlates with outcome, as it often does for agents, they can also change its direction.
- Preconditioned optimizers. An update with a fixed positive-definite preconditioner changes the relevant alignment to , and its sign can differ from the Euclidean . Adam’s preconditioner also depends on the gradients themselves, so this is a first approximation there.
- Dynamic sampling. Filtering out groups in which every rollout passes or every rollout fails, as in DAPO (Yu et al., 2025), keeps the binary update parallel to but gives no signal on a prompt that never succeeds. The fallback exists precisely to use the groups that dynamic sampling discards.
- Clipping and several epochs per batch. At the behavior policy the clipped surrogate has the same gradient as the unclipped objective, so the results describe the first step. They are not guarantees about later steps or about the final policy.
Propositions 1 to 5 hold for any score assigned to a whole trajectory. The verifier thresholds after Proposition 2, the comparison with the fixed mixture, Proposition 6 and the worked examples also use the structure of fractional return, namely that every success scores one and that the return is built from individual checks.
A practical rule
For a real training run, the first questions are operational rather than philosophical.
- Is the fallback active? Measure the all-fail-group frequency and the fraction of all-fail groups with nonconstant . If fractional return is constant within nearly every all-fail group, there is no fractional-return signal to use.
- Which way does it pull? Estimate from rollouts the trainer already has. It needs the mean trajectory score over successes and the mean score over failures weighted by , where is the mean fractional return of the failures. Each is the gradient of a weighted sum of log-probabilities, so each costs one backward pass. Noise inflates , so compute the denominator from two disjoint halves of the successes. Under a preconditioned optimizer, take the inner products in the optimizer’s geometry. The distribution of alone cannot answer this question.
- Know where it cannot be measured. requires successes, so it cannot be estimated on prompts that never complete, which are exactly the prompts where the fallback fires most. Count how many prompts never complete during the run, since for them the fallback is the only signal. Pooling across prompts that do complete estimates a corpus-level quantity, not the missing per-prompt one.
- Does the model improve the right endpoint? Report all-pass success as the primary metric, and track only as a diagnostic. Rising fractional return with declining completion is evidence of the failure mode above. Rising fractional return with flat completion is not, by itself, evidence of harm. On hard prompts that is also what healthy learning looks like at first. With ten independent checks each improving from 0.5 to 0.6, rises from 0.50 to 0.60 while moves only from 0.001 to 0.006.
The point is not to retreat to binary-only learning. On hard verifier tasks, that discards variation the verifier already provides. The point is to preserve the information in a decomposable verifier while refusing to let a fractional-return shortcut outrank completion.
Closing thought
Fractional return is valuable precisely because it is not arbitrary. It comes from the same checks that define success. In a benign competence regime, it gives completion-aligned signal exactly where binary GRPO is silent. But decomposition is not the same as alignment. Once an agent can reach the same checks through competing strategies, a terminal fractional return can optimize a more attractive failure instead of completion.
The right response is neither to discard fractional return nor to mix it blindly with a large binary coefficient. Letting completion decide every comparison it can removes the conflict inside each group. What remains lives across groups, and it matters mostly when a few hard, loosely related tasks are revisited many times. There, it is worth measuring to check that the fractional branch still points toward the endpoint that matters.
Binary gating is also a building block rather than a complete recipe. Behaviors that must never be reinforced, such as breaking tests that used to pass, can be made part of the completion criterion or can zero the fallback’s return, and Propositions 1 to 5 hold unchanged for the redefined returns. Nor does gating have to discard fractional return inside mixed groups. A binary-anchored label keeps every binary sign and lets fractional return rescale magnitudes within each outcome class (Appendix A.8). It carries the same guarantee as Proposition 3, but its mixed-group term is then no longer the pure completion gradient, so its expected update deserves the same scrutiny as the fallback.
References
- Shao, Z., et al. (2024). DeepSeekMath: Pushing the limits of mathematical reasoning in open language models.
- Yu, Q., et al. (2025). DAPO: An open-source LLM reinforcement learning system at scale.
Appendix A. Proofs and derivations
This appendix collects the proofs of Propositions 1 to 6, the computation behind the three-strategy table, and the guarantee for the binary-anchored label.
A.1 Proof of Proposition 1
By construction,
Hence, for every ,
Expanding the square gives
where . If , then is not almost surely zero, so and this is a strictly convex quadratic in . Its minimizer is
and the reduction at that point is
If the numerator is positive, every sufficiently small positive improves the corresponding binary-only target. Since is the best binary-only target, taking and proves the dominance claim in Proposition 1.
A.2 Proof of Proposition 2
For a failed rollout in a mixed group, and . Also,
Therefore exactly when
which rearranges to the stated condition.
For a terminal fractional return, every successful rollout has , so . If failures can score anywhere from 0 up to , the largest possible gap is , attained when rollout scores and every other failure scores zero. Substituting it into the positive-label condition shows that a reversal is possible exactly when
Across all verifiers, can be arbitrarily close to one, which gives the bound . Any smaller admits a reversal for some verifier, and no at or above it admits one for any verifier.
A.3 Proof of Proposition 3
In a mixed group, . If rollout succeeds,
If it fails,
The fractional branch is not used in either calculation.
A.4 Proof of Proposition 4
Let denote a generic trajectory score, so . For any terminal scalar with no explicit parameter dependence, inclusive group centering gives
because by the score-function identity, the term of the group mean removes from it, and the terms vanish by independence and .
Centered binary return is zero on all-pass and all-fail groups, so the binary-gated label can be written as . The first part is centered binary return, whose expected update is .
Now condition on the all-fail event. It has probability , and conditional on that event the rollouts are independent draws from the policy conditioned on . The conditional score is not zero in general, so the identity above does not apply directly. Expanding the group mean instead, the diagonal terms give and each off-diagonal term gives by conditional independence. Hence
Since , differentiating gives
Multiplying by the all-fail probability and by yields the second term of Proposition 4.
The same centering identity with gives the fixed-mixture update. Since ,
and therefore .
A.5 Proof of Proposition 5
By A.4, , so
Since is binary, . Therefore
Taking the inner product of Proposition 4 with and dividing by gives
Binary GRPO has expected update , whose normalized projection is exactly . With , , and , the binary-gated projection exceeds binary GRPO’s exactly when , and it is positive exactly when . The same computation applied to the fixed-mixture update in A.4 gives .
For a preconditioned update with symmetric positive definite, the same steps with inner products replace by .
A.6 Proof of Proposition 6
Let , let
and write , so . Since is the unweighted pass fraction,
Because on the all-pass event,
Clearly
Differentiating gives
Set for . The numerator is positive precisely when
This holds because
and because and every lies in , the final inequality is strict. Hence .
Let denote the Jacobian of a parameterization in which every check probability is nondecreasing in every parameter. For every parameter coordinate ,
Therefore,
If , some coordinate has , which requires for some . For that , , so the inner product is strictly positive. By A.5, , so has the same sign. This proves the result.
A.7 The three-strategy table
Write for the probability of strategy , for its completion probability, and for the fractional return of its failures, so that is , and for the three strategies. With logits and gradients taken with respect to , the softmax identity gives, for any per-strategy quantity with mean ,
Apply this with , whose mean is , and with , whose mean is . Since and ,
and by A.5, . With , these formulas give , and the column of the table. The progress column is with and .
A.8 The binary-anchored label
In a mixed group, both outcome classes are nonempty. For , let be the mean fractional return of the rollouts with , and let be the deviation of rollout from the mean of its own class. The binary-anchored label is
It differs from the binary-gated label only in mixed groups. There it assigns a strictly positive label to every successful rollout and a strictly negative label to every failed rollout, and its labels sum to zero.
Because , every deviation satisfies , so
Each label therefore has the sign of , which A.3 shows is positive for successes and negative for failures. For the sum, , and within class the correction terms add up to , because deviations from a class mean sum to zero.
For a terminal fractional return, every success has , so on successes and anchoring rescales only failures. A failed rollout receives , so a failure that scores above the failure mean is pushed down less than one that scores below it. The expected mixed-group term is therefore generally not . It carries an additional term that, like the fallback, favors higher-scoring failures.


Mehdi Fatemi is a Principal Research Scientist at Snorkel AI and a reinforcement learning (RL) researcher with more than 15 years of experience, beginning with his PhD at McMaster University. His work spans the foundations and applications of RL, including value-based methods, long-horizon and multi-turn decision-making, and, over the past few years, reasoning in large language models under diverse feedback signals and uncertainty. Previously, during several years at Microsoft Research, he made numerous core contributions to RL through papers, patents, and public releases, including Hybrid Reward Architecture for learning from decomposable rewards and dead-end theory for identifying and avoiding irrecoverable states. His recent work includes Concise Reasoning, which shows that RL’s loss alone drives reasoning models toward verbosity or conciseness, depending on the solvability of the training tasks.
Recommended articles









