Bring the mental model from RLHF: Reward Modeling + KL-Regularized Policy Optimization; this page will reuse it instead of restarting from zero.
Alignment
Process Reward Models: Step-Level Verifiers for Reasoning
A process reward model scores intermediate reasoning steps instead of only terminal answers, giving denser verifier feedback for reranking and search while remaining a learned proxy.

Concept Structure
Process Reward Models: Step-Level Verifiers for Reasoning
Start with the picture, metaphor, or geometric mechanism.
Make the objects explicit and connect them with notation.
Mirror the equations with runnable implementation details.
Manipulate the mechanism and watch the idea respond.
Learning map
Process Reward Models: Step-Level Verifiers for ReasoningConceptual Bridge
What should feel connected as you move through this page.
A process reward model scores intermediate reasoning steps instead of only terminal answers, giving denser verifier feedback for reranking and search while remaining a learned proxy.
The next edge should feel earned: use the demo prediction here before following Test-Time Compute: Spending Inference Budget on Search.
01
Intuition
Build the mental picture first so the rest of the page has something to attach to.
Canonical sources: Lightman et al., "Let's Verify Step by Step", the OpenAI prm800k dataset release, Uesato et al., "Solving math word problems with process- and outcome-based feedback", Cobbe et al., "Training Verifiers to Solve Math Word Problems", and Snell et al., "Scaling LLM Test-Time Compute Optimally".
An outcome reward model asks one terminal question: did the final answer look correct?
A process reward model asks a local question at every step: given the prompt and the reasoning prefix so far, is this next step valid?
That changes the shape of feedback. Instead of treating a whole solution as one indivisible completion, the verifier sees a path through intermediate states. A lucky final answer with broken reasoning can receive high outcome reward and low process reward. A trace with one early algebra mistake can be rejected before the mistake compounds.
The important caveat is that a process reward model is still a learned proxy. It can localize errors better than terminal-only feedback, but its step labels can be ambiguous, expensive, domain-limited, or wrong. PRMs do not solve reward hacking; they move the proxy from the leaf of the reasoning tree onto the edges.
02
Math
Translate the story into symbols, assumptions, and a derivation you can inspect.
Fix one prompt . In this page's binary teaching notation, a process reward model sees a reasoning prefix and a candidate next step, then predicts whether that step is locally correct. Lightman et al.'s PRM800K labels include positive, negative, and neutral ratings; here we collapse the idea into correct vs. not-correct to expose the verifier mechanics.
For labeled steps , the binary verifier can be trained with cross-entropy:
A complete solution is a terminal trace
Outcome supervision observes only a terminal label
For a terminal trace, one simple additive score is the sum of step logits:
Other aggregations, such as mean step probability, product of step probabilities, or minimum step score, are design choices rather than a universal PRM definition. The key definition is local verification of steps.
Separate from Lightman et al.'s best-of-N evaluation, this page also shows a finite KL-style RLHF bridge. A KL-regularized trajectory update is
This is the same finite-action probability-shaping pattern as RLHF, but the learned reward decomposes over reasoning steps. Smaller pushes harder on the verifier score. If the step verifier is wrong, optimization can still select verifier error.
03
Code
Keep the implementation aligned with the notation so the algorithm is legible.
This witness uses four fixed traces for the equation . The outcome verifier prefers a trace with the correct final answer but invalid reasoning. The accurate process verifier prefers the clean trace. If we inject a false-positive process error, the process verifier can be fooled too.
import math
import numpy as np
def logit(p):
p = min(max(p, 1e-6), 1 - 1e-6)
return math.log(p / (1 - p))
def policy(scores, ref, beta=0.7):
logits = np.log(ref) + np.asarray(scores) / beta
logits = logits - logits.max()
weights = np.exp(logits)
return weights / weights.sum()
traces = ["clean", "lucky_final", "slip", "wrong"]
ref = np.array([0.30, 0.22, 0.28, 0.20])
outcome_p = np.array([0.86, 0.92, 0.16, 0.12])
step_p = [
[0.93, 0.91],
[0.16, 0.24],
[0.93, 0.22],
[0.20, 0.35],
]
def process_scores(step_probs):
return [sum(logit(p) for p in probs) for probs in step_probs]
outcome_winner = traces[int(policy([logit(p) for p in outcome_p], ref).argmax())]
process_winner = traces[int(policy(process_scores(step_p), ref).argmax())]
hacked_steps = [list(probs) for probs in step_p]
hacked_steps[1] = [0.98, 0.97]
hacked_winner = traces[int(policy(process_scores(hacked_steps), ref).argmax())]
print(outcome_winner, process_winner, hacked_winner)
assert outcome_winner == "lucky_final"
assert process_winner == "clean"
assert hacked_winner == "lucky_final"
04
Interactive Demo
Use direct manipulation to connect the explanation to a moving system.
Use the demo as a diagnostic instrument. Switch between outcome-only scoring and process scoring, change the process aggregation, inject verifier errors, and lower to increase optimization pressure. Watch how probability mass moves across complete traces, and whether the selected trace has a correct final answer, valid local steps, or merely a high verifier score.
Live Concept Demo
Explore Process Reward Models: Step-Level Verifiers for Reasoning
The stage is code-native and interactive. Use it to test the explanation against the mechanism.
Manipulate one control and predict the visible change.
Commit to what Process Reward Models: Step-Level Verifiers for Reasoning should make visible before reading the result.
After The First Pass
Turn the concept into an inspected object.
Once the invariant is visible in the intuition, math, code, and demo, use these panels to inspect the mechanism visually, check source support, practice the idea, and attach a grounded research question.
Mechanism Storyboard
See the idea move before the page explains it
A process reward model scores intermediate reasoning steps instead of only terminal answers, giving denser verifier feedback for reranking and search while remaining a learned proxy.

Start with the picture, metaphor, or geometric mechanism.
Before reading further, choose the kind of change Process Reward Models: Step-Level Verifiers for Reasoning should make visible.
Visual Inquiry
Make the image answer a mathematical question
A process reward model scores intermediate reasoning steps instead of only terminal answers, giving denser verifier feedback for reranking and search while remaining a learned proxy.
Which visible object should carry the first intuition?
Pick the cue that should make Process Reward Models: Step-Level Verifiers for Reasoning easier to reason about before the page gives the answer.
Source Grounding
Canonical references for the mechanism on this page.
Grounds process supervision and PRM800K as step-level feedback for mathematical reasoning traces.
Open sourceClaim Review
A process reward model scores intermediate reasoning steps instead of only terminal answers, giving denser verifier feedback for reranking and search while remaining a learned proxy.
Claims without a substantive review badge still need exact source-support review.
lightman-2023-verify-step-by-step
Use equation, code, and demo objects to check whether the source support is operational.
Lightman et al. contrast ORMs using final results with PRMs receiving feedback for each step, train PRMs to predict step correctness, reduce step scores for solution ranking, and evaluate by best-of-N search. Local math gives the binary verifier and BCE teaching form; code/demo witness outcome vs process selection and verifier-error/proxy failure.
Sources: Let's Verify Step by StepBinary Bernoulli/BCE is a teaching reduction; Lightman use positive/negative/neutral labels and token log-likelihood. Excludes exact aggregation, calibration, KL/RL generator training, universal gains, cheap labels, reward-hacking prevention, and broad alignment guarantees.A bounded review summary is present; still check caveats and exact source scope.Lightman et al. support PRMs as process-supervised reward models trained on step-level labels and evaluated by best-of-N selection of the highest-ranked generated solution. The page's binary Bernoulli/BCE notation is a didactic collapse of their positive/negative/neutral token-likelihood setup. PRM reliability/proxy limits are supported by their reward-model mistake/false-positive examples. KL reweighting is outside this reviewed claim.
Reviewer: codex+oracle; reviewed 2026-05-07Practice Loop
Try the idea before it explains itself
A process reward model scores intermediate reasoning steps instead of only terminal answers, giving denser verifier feedback for reranking and search while remaining a learned proxy.
Before touching the demo, predict one visible change that should happen in Process Reward Models: Step-Level Verifiers for Reasoning.
Reveal when your model needs a nudge.
Reveal when your model needs a nudge.
Reveal when your model needs a nudge.
A concrete answer is on the canvas.
The answer names why the claim should hold.
It touches the page context or a neighboring idea.
Research Room
Attach the question to an exact object
Pick the concept, equation, source, code witness, claim, misconception, or demo state before asking for help. The handoff stays grounded to that object.Open the draft below to save one note and next action in this browser.
Process Reward Models: Step-Level Verifiers for Reasoning
What is the smallest example that makes Process Reward Models: Step-Level Verifiers for Reasoning click without losing the math?
Local action draftNo local draft saved yetExpand only when ready to capture one local next action
This draft stays locally in this browser for concept:alignment/process-reward-models.
- Source ids to inspect: lightman-2023-verify-step-by-step
- Definition, prerequisite, and contrast concept links
- The equation or code witness that makes the concept operational
- One demo state that shows the invariant instead of a slogan
- The learner can state the mechanism in their own words
- The learner can name the prerequisite that would repair confusion
- The learner can predict how the mechanism changes under one perturbation
I am working in Continuous Function's research reading room. Object: concept - Process Reward Models: Step-Level Verifiers for Reasoning Object key: concept:alignment/process-reward-models Context: Alignment Anchor id: concept/concept-notebook/alignment/process-reward-models Open question: What is the smallest example that makes Process Reward Models: Step-Level Verifiers for Reasoning click without losing the math? Evidence to inspect: - Source ids to inspect: lightman-2023-verify-step-by-step - Definition, prerequisite, and contrast concept links - The equation or code witness that makes the concept operational - One demo state that shows the invariant instead of a slogan What would resolve this: - The learner can state the mechanism in their own words - The learner can name the prerequisite that would repair confusion - The learner can predict how the mechanism changes under one perturbation Answer as a careful research tutor: stay source-grounded, separate verified evidence from assumptions, name the relevant math objects, and end with one next action.
concept/concept-notebook/alignment/process-reward-models
concept:alignment/process-reward-models