Progress-Potential Reward Shaping
Long-horizon rollouts can all fail and give group-relative training no useful contrast; progress-potential reward shaping scores prerequisite-aware workspace progress and rewards its changes along the way.
Read the paper ↗What it is
- Progress potential A score for how much of the expected workspace has been completed correctly, with downstream credit limited by the correctness of prerequisite work.
- Progress-potential reward shaping Training rewards changes in that workspace score and also retains a final progress component, while still giving verified completion the highest trajectory reward.
- Per-turn group-relative credit Progress changes are assigned to turns, so rollouts in a group can be compared even when none reaches a passing submission.
Why it matters
Long tasks often produce batches where every attempt fails. A grounded progress score gives the trainer useful differences between those attempts, instead of treating a careful near-miss like a rollout that did nothing.
Before getting into the mechanics, the simple version is this: instead of waiting until an agent submits a finished workspace to decide whether it learned anything, score the workspace as it changes. That gives training a way to tell a near-miss from a rollout that went nowhere, while keeping the strict verifier as the definition of success.
-
Sparse outcomes: With terminal-only reward, a group where every rollout fails gets the same zero reward everywhere. In group-relative training, there is then no contrast to learn from. The paper’s motivating example is a long-horizon task where an untrained model may have a low chance of solving it, so all-fail groups are common.
-
Dependencies matter: A pile of partly correct files is not necessarily meaningful progress. The canonical example is a data workflow: an aggregate may look plausible, but if it was built on a wrong fact table, downstream correctness has not been earned. The progress score therefore checks intermediate workspace artifacts against the latent world and caps a node’s credit by its prerequisites. Think of a notebook where you can erase a page or carry a flawed page forward; the limit of the analogy is that the scorer compares artifacts to ground truth rather than relying on a person’s judgment.
-
Credit over time: The trainer needs to know not just where a rollout ended, but which turns improved or damaged the workspace. Before the equation, the mechanism is simple: compare the current workspace score with the previous one; an improvement earns an increment, and a regression earns a negative increment. This is the potential difference, . In words, each step gets the change in progress score.
So the real question was never just how to make reward denser—it was whether partial progress should affect the objective at all. PPRS retains a terminal progress term as well as the strict terminal pass reward: . In words, the final return includes both verified success and weighted progress in the final workspace. The reported setting uses . Unlike policy-invariant potential shaping, this intentionally values progress; still, any passing rollout outranks a failing one. What happens when an entire group fails? Different progress levels give different returns, unless every rollout stalled at the same stage.
Read the deep dive
Why People Wanted It
A terminal-only reward answers one question: did the agent submit a workspace that passed the strict verifier? That is the right acceptance test, but it is a poor training signal when a whole group of rollouts fails. In group-relative learning, identical failure rewards leave no within-group contrast, so the task contributes nothing to the gradient. The real question is how to keep the acceptance test strict while distinguishing a useful near-miss from a rollout that made no progress.
The Core Move
Score the workspace against prerequisite-aware checks of correct intermediate artifacts, then reward changes in that score while retaining a terminal progress term. The source states the shaping equations as follows:
Here the rollout reward is the terminal pass reward plus a weighted final potential; the step reward is the change in workspace potential. The reported runs use . No further equation for the potential is needed to state its defining construction: it is a weighted sum of prerequisite-gated node scores.
Why Prerequisites Gate Progress
Now the version for readers who want more of the machinery: a workspace check cannot earn full credit for a downstream artifact if one of its dependencies is wrong. Each environment has progress-contract nodes, positive node weights that sum to one, and prerequisite sets. For node , the partial scorer grades the current workspace directly against the latent world. The gated score is the lowest partial score across and all its direct and indirect prerequisites. The potential is the weighted sum of those gated scores.
This is a constraint on credit, not merely a preference for completing tasks in a particular order. For example, an aggregate built on an incorrect fact table gets no credit for that node. In the warehouse example, relations require dimensions and facts. The resulting potential is anchored: the untouched public tree and probed gaming strategies score zero, and the potential is one exactly when the strict verifier accepts. It is monotone with completed work and falls when completed work is destroyed. The scorer is independent in the sense that its code closure is disjoint from the verifier and reference solvers.
Why Keeping the Terminal Potential Changes the Objective
Here is the part that gets technical: classical potential-based shaping removes the terminal potential so that shaping does not change the original objective. PPRS keeps it. Thus the terminal reward is success plus , deliberately making partial progress matter to the training objective. Because , a passing rollout earns , while a failing rollout earns at most ; completion still ranks above failure. The acceptance set is unchanged, but expected rankings of stochastic policies need not be.
The reward depends on the final workspace, not the route taken to reach it: rollouts ending in the same workspace receive the same reward even if their step order or implementation differs. A rollout that uses up its budget without submitting receives the terminal progress term alone; submission is an action, not a workspace state.
Why Per-Turn Credit Helps Group-Relative Learning
Now the training-level consequence: each turn receives its potential increment, scaled by , and the final turn additionally receives the terminal term. Return-to-go is compared with the group mean at the same turn index. If every rollout fails, their terminal pass rewards are all zero, but differing final potentials produce differing returns and therefore nonzero group-relative advantages when the group made differing progress. If all rollouts stall at the same stage, that contrast is absent.
Minimal Causal Code
This loop makes the state change visible. It records the potential difference at each turn and adds the terminal term separately; it is illustrative, not the paper's full training implementation.
# phi(workspace) returns the prerequisite-gated potential in [0, 1].
lam = 0.25
state = initial_workspace
previous_phi = phi(state)
turn_rewards = []
for action in rollout:
state = apply_action(state, action)
current_phi = phi(state)
increment = current_phi - previous_phi
turn_rewards.append(lam * increment)
previous_phi = current_phi
terminal_pass = strict_verifier(state) if submitted else 0.0
if turn_rewards:
turn_rewards[-1] += terminal_pass + lam * previous_phi
What You Gain, and What You Lose
PPRS can give group-relative training a ranking signal even when no rollout passes, and its prerequisite gates tie that signal to grounded intermediate work rather than arbitrary activity. Per-turn increments also make regressions visible as negative reward changes.
The price is a deliberately changed objective: partial progress now matters, and stochastic-policy rankings can differ from those under terminal success alone. The approach depends on an exact, task-aligned scorer; a misaligned potential could reward the wrong behavior. The scoring system is designed to be anchored, monotone, and independent, but those properties are substantive requirements, not automatic consequences of adding a shaping term.
Keep the pass gate strict, but let grounded progress distinguish failures that terminal reward would treat alike.