Starting checkpoints and behavioral targets
A checkpoint saves fitted model state, including parameter tensors and potentially registered buffers. Restoring it requires the corresponding model structure. Resuming training usually also requires optimizer state and other records; a weights file alone does not reproduce an entire run. The PyTorch checkpoint guide distinguishes these uses.
A policy assigns probabilities to possible outputs given context. For an autoregressive language model, it predicts the next token from the prompt and preceding tokens. Post-training changes learned parameters; ordinary prompting changes the input to fixed parameters. Training versus inference explains that boundary, while Pretraining and Midtraining covers the starting model's production.
Training and assessment take separate paths
ExampleA requirement shapes supervision and independent acceptance criteria.
Read the diagram as text
- Behavioral requirements.
- Demonstrations, pairs, or rewards.
- Starting checkpoint.
- Adapt parameters.
- Candidate checkpoint.
- Independent behavioral assessment.
- Behavioral requirements → Demonstrations, pairs, or rewards: defines training targets.
- Behavioral requirements → Independent behavioral assessment: defines acceptance criteria.
- Demonstrations, pairs, or rewards → Adapt parameters: supplies learning signal.
- Starting checkpoint → Adapt parameters: supplies fitted parameters.
- Adapt parameters → Candidate checkpoint: produces updated parameters.
- Candidate checkpoint → Independent behavioral assessment: produces evaluated behavior.
Alignment means adapting behavior toward stated human goals and constraints. A specification can guide both training feedback and separate assessment cases. Its requirements must identify whose needs govern and how conflicts are resolved; approval under one rubric cannot stand for universal human preference. Intended outcomes and evaluation boundaries supplies the corresponding assessment framework.
For a programming assistant, stipulate three requirements: solve supported legitimate tasks, acknowledge insufficient evidence, and refuse specified harmful requests while assisting safe ones. These are teaching requirements, not reported experimental results. Demonstrations, comparisons, and rewards can each encode parts of them.
Supervised fine-tuning from desired responses
Supervised fine-tuning, or SFT, trains an existing model on supplied input–target examples. With teacher forcing, each prediction conditions on the demonstrated prefix, including its mistakes. A loss mask selects targets for direct supervision; an attention mask controls information visibility. Excluding prompt targets from loss does not remove the prompt from context.
Context is not the same as supervision
Excluded prompt targets can still condition every supervised prediction.
Read the diagram as text
- Prompt and recorded response prefix.
- Next-token probabilities.
- Recorded targets and loss mask.
- Selected target loss.
- Parameter update.
- Prompt and recorded response prefix → Next-token probabilities: conditions predictions.
- Next-token probabilities → Selected target loss: supplies target probabilities.
- Recorded targets and loss mask → Selected target loss: selects supervised terms.
- Selected target loss → Parameter update: supplies gradients.
Completion-only supervision includes the completion; assistant-only supervision selects assistant turns; full-sequence supervision can include prompt targets. Padding is excluded. The chosen mask, conversation template, and dataset must agree.
Assume a short record has five token units: USER, ping, ASSISTANT, OK, END. These are stipulated boundaries, not a tokenizer claim. With response-only supervision, the prompt remains available while only OK and END contribute loss. The probabilities below are example values.
| Conditioning prefix | Next target | Mask | Target probability |
|---|---|---|---|
| USER | ping | 0 | Excluded |
| USER ping | ASSISTANT | 0 | Excluded |
| USER ping ASSISTANT | OK | 1 | 0.50 |
| USER ping ASSISTANT OK | END | 1 | 0.25 |
Using natural logarithms, the included loss is ; averaging over two targets gives approximately 1.040. Backpropagation differentiates that scalar with respect to parameters. The optimizer uses those gradients to update the checkpoint. A gradient describes local loss sensitivity, not a symbolic instruction to repair one behavior; see Gradients and parameter updates.
Aggregation changes effective weighting. Summing token losses gives longer responses more terms; averaging within each example before averaging examples changes that balance. Repeating or sampling an example more often increases its contribution. These choices determine which demonstrated patterns dominate, alongside explicit weights and task coverage.
SFT is useful for specified output mappings such as extraction and formatting. Its target remains the supplied answer: flawed facts or stylistic shortcuts can receive the same imitation signal. Generated demonstrations are still training inputs. Their construction belongs to Synthetic Data; improvement requires separate assessment.
Preference pairs and judgment meaning
A preference pair contains two responses to the same prompt and a comparative judgment under a rubric, the criteria for judging them. The selected response is called chosen; the other is rejected. These labels express relative preference, not absolute adequacy.
A constructed pair answers whether passing supplied tests establishes correctness on every input. Response A states that untested inputs remain unresolved. Response B enthusiastically congratulates the programmer and asserts universal correctness. Hold these responses fixed while changing the stipulated judgment criterion.
| Stipulated criterion | Chosen response | What the label conveys |
|---|---|---|
| Factual support first | A | Limited evidence should not support universal certainty. |
| Enthusiasm and affirmation only | B | Approval can favor an unsupported assertion. |
Candidate collection determines available contrasts. Preserve prompt coverage, generating checkpoints, sampling settings, judge identity or model version, and rubric version. Comparisons between nearly identical answers teach different distinctions from comparisons that isolate a factual error. The summarization research operationalized selected labelers' judgments under researcher-defined requirements, rather than discovering a population-independent preference.
A tie, an uncertain judgment, and disagreement between judges are different records. A binary chosen/rejected objective requires an explicit policy for including or adjudicating them; silently inventing a winner changes the target. Preserve the underlying judgments. Label meaning and Annotation, disagreement and correction explain the broader data responsibilities.
Sampling from the model being adapted can expose its current failures. One small-model recipe ranked looping and non-looping candidates to construct preference pairs. That approach needs both a useful alternative and a judge that actually penalizes repetition.
Learned rewards from comparisons
A reward model assigns a scalar score to prompt and response . Bradley–Terry modeling learns preferences through score differences.
| Example chosen score | Rejected score | Modeled preference probability |
|---|---|---|
| ln(3) | 0 | 0.75 |
| 5 + ln(3) | 5 | 0.75 |
Adding a common offset leaves comparisons unchanged. The resulting probability concerns preference, not factual correctness. Moreover, a majority cycle—A preferred to B, B to C, and C to A—cannot fit a strict scalar ordering. Disagreement alone need not create such a cycle.
A scorer can learn shortcuts in its labels. In a video-judge example, manufactured negatives encouraged detecting visual artifacts instead of the intended quality dimensions. Responses generated after optimization may expose further weaknesses. Automated judge reliability covers judging validity; using a scorer as a reward adds pressure to exploit its errors.
Executable rewards and checker contracts
A verifier applies an explicit checking procedure. A test oracle decides whether observed behavior meets its criterion. A verifiable reward converts such checking into training feedback. Automatic computation does not expand the checked property; Oracles, rubrics and human judgments explains this distinction.
| Checker | Acceptance establishes | Important exclusions |
|---|---|---|
| Supplied code tests | The observed execution satisfies those assertions. | Untested inputs and omitted requirements remain unchecked. |
| Final-answer equivalence rule | The extracted answer satisfies the specified comparison. | Parser limitations and the validity of preceding reasoning. |
| Lean proof checking | The formal theorem follows under its definitions and assumptions. | Whether the formal statement captures the intended problem and whether all assumptions are permitted. |
Checkers can also reject valid alternatives. Tests that demand an unspecified variable name or inspect an internal function constrain implementation beyond the requested behavior. Such false negatives supply misleading penalties, just as missing assertions can supply misleading rewards.
A successful formal proof check needs a dependency audit: imported results can depend on incomplete proofs or custom axioms. Lean's validation contract therefore matters when defining allowed assumptions. Checking an intermediate formal claim is possible under the same contract; that possibility alone establishes no effective intermediate-reward training procedure.
Outcome and intermediate feedback
Outcome supervision assesses a completed result. Process supervision assesses intermediate steps, requiring a definition of a step and a defensible judgment about it. Feedback location and feedback source are separate choices.
Sparse reward supplies feedback at few points, often only completion. Credit assignment connects that delayed outcome to earlier choices. A return aggregates rewards; it does not identify causal responsibility. A correct terminal answer may follow mistakes, while useful intermediate work may occur in a failed attempt.
Correct outcomes can conceal defective steps
ExampleFinal-answer acceptance and step approval assess different properties.
Read the diagram as text
- Evaluate (2+3)−1.
- Written step: 2+3=6.
- Written conclusion: 6−1=4.
- Learned step judgment: incorrect.
- Executable final check: accepted.
- Evaluate (2+3)−1 → Written step: 2+3=6: response begins.
- Written step: 2+3=6 → Written conclusion: 6−1=4: response continues.
- Written step: 2+3=6 → Learned step judgment: incorrect: intermediate assessment.
- Written conclusion: 6−1=4 → Executable final check: accepted: extract final answer.
- Evaluate (2+3)−1 → Executable final check: accepted: expected answer: 4.
In one mathematical process-supervision study, human step labels trained a learned scorer, while final-answer checks supplied outcome labels. Multiplying predicted step-correctness probabilities ranked solutions. The generator stayed fixed during best-of-N evaluation: those results concern selecting generated solutions, not reinforcement learning of the generator.
An approved prefix can still lead to a wrong answer. Conversely, the illustrated arithmetic trace reaches the correct answer through a defective intermediate equation. Assessing written steps also differs from establishing explanation faithfulness: behavioral interventions can reveal influences on an answer that its explanation omits.
Long agent trajectories sharpen the problem. Assigning the same final return to every model call treats helpful, needless, and mistaken actions alike. A transition-level record permits more selective assignment, but does not itself discover which action caused success. Changing an action in a counterfactual test also requires recomputing downstream observations.
Reinforcement learning for response policies
For language-model reinforcement learning, tokens are actions and the prompt plus generated prefix supplies their context. A rollout is a sampled continuation, extended to actions and observations for interactive tasks. Sampling, scoring, and updating weights produces a new policy for subsequent sampling. Actions and rewards provides the underlying learning framework.
An advantage compares return with a baseline. Positive advantage favors sampled choices; negative advantage suppresses them. Policy gradients differentiate output log-probabilities. When the environment and scorer do not depend on policy parameters, training need not differentiate through them.
Updated policies produce fresh training samples
ExampleA rollout retains the identity of the checkpoint that generated it.
C0 generates B0.
Read the diagram as text
- Policy learner.
- Checkpoint C0.
- Rollout batch B0.
- B0 scores.
- Checkpoint C1.
- Fresh rollout batch B1.
- Policy learner → Checkpoint C0: starts from.
- Checkpoint C0 → Rollout batch B0: samples.
- Rollout batch B0 → B0 scores: external grading.
- Checkpoint C0 → Checkpoint C1: parameter update.
- B0 scores → Checkpoint C1: guides update.
- Checkpoint C1 → Fresh rollout batch B1: resamples.
- Sample. C0 generates B0. Active: Policy learner, Checkpoint C0, Rollout batch B0. New: Policy learner, Checkpoint C0, Rollout batch B0.
- Score. New feedback assesses the retained B0 responses. Active: Policy learner, Checkpoint C0, Rollout batch B0, B0 scores. New: B0 scores.
- Update and resample. C1 and B1 are new; C0, B0, and their feedback remain visible. Active: Policy learner, Checkpoint C0, Rollout batch B0, B0 scores, Checkpoint C1, Fresh rollout batch B1. New: Checkpoint C1, Fresh rollout batch B1.
for _ in range(rounds):
samples = sample(policy, prompts)
rewards = score(samples).detach()
advantage = (rewards - baseline).detach()
logp = policy.token_logprobs(samples)
loss = -(advantage[:, None] * logp * samples.mask).sum(-1).mean()
optimizer.zero_grad()
loss.backward()
optimizer.step()For example rewards , a baseline of gives advantages . The failed response receives a negative direction; the two successes receive positive directions. This does not label every token correct or determine exact new probabilities: responses share parameters and interact during optimization.
RLHF uses human feedback, often through a learned preference reward. RLVR uses verifiable rewards. These name feedback sources, not interchangeable optimizer specifications.
Group Relative Policy Optimization, or GRPO, replaces a learned value baseline with comparisons among responses to one prompt. Its original outcome version uses , where is response reward and are group mean and standard deviation. Each response token shares that advantage; clipped ratios and reference KL enter separately.
Equal group rewards make the written normalization undefined. Code must handle zero spread explicitly; with denominator stabilization, the relative reward signal is zero, although KL can still contribute gradients. GRPO can use learned rewards or executable checks. Removing the value model and replacing a learned reward model are separate decisions.
Sparse success leaves little useful contrast. More varied sampling can expose better trajectories, but excessive randomness can break coherent output. On-policy means sampling from the policy being trained; it does not mean the prompts represent production use. Task coverage and exploration remain separate design choices.
Reference regularization and PPO clipping
A reference policy remains fixed at a designated starting checkpoint. The trainable policy changes. A separate, recent rollout snapshot records the policy that generated a batch; it need not equal the reference.
Two policy comparisons serve different roles
The rollout snapshot and fixed reference are distinct.
Read the diagram as text
- Rollout snapshot.
- Trainable policy.
- Fixed reference.
- Clipped surrogate.
- Reference KL.
- Parameter update.
- Rollout snapshot → Clipped surrogate: ratio denominator.
- Trainable policy → Clipped surrogate: ratio numerator.
- Trainable policy → Reference KL: current distribution.
- Fixed reference → Reference KL: reference distribution.
- Clipped surrogate → Parameter update: reward-directed incentive.
- Reference KL → Parameter update: drift penalty.
Proximal Policy Optimization, or PPO, modifies incentives relative to the rollout policy. A critic, or value model, estimates expected return to help estimate advantages; it does not judge answer correctness.
With , , and , the surrogate is 2.4 instead of 2.8. With and , it is −1.6 instead of −1.2. These favorable changes stop earning extra incentive. Harmful changes still count: increasing a negative-advantage action to gives −2.8.
ratio = exp(logp - old_logp.detach())
advantage = advantage.detach()
unclipped = ratio * advantage
clipped = ratio.clamp(1 - epsilon, 1 + epsilon) * advantage
policy_loss = -minimum(unclipped, clipped).mean()Clipping removes an incentive; it does not impose a hard probability bound. Shared parameters and other objective terms can still change a clipped action's probability. PPO may reuse a batch over several minibatch epochs. Its old-policy ratio remains distinct from a fixed-reference KL penalty.
Direct preference optimization
Direct Preference Optimization, or DPO, trains the response policy directly from comparisons. Sequence log-probability sums conditional token log-probabilities. Original offline DPO uses fixed pairs and reference probabilities, without fitting a separate reward network or sampling fresh responses during each update.
Comparisons can train a scorer or a policy
Offline DPO removes separate reward fitting.
Read the diagram as text
- Preference pairs.
- Fit reward model.
- Fresh policy samples.
- Reward-guided policy update.
- Policy/reference pairwise loss.
- Direct policy update.
- Preference pairs → Fit reward model: RLHF route.
- Fit reward model → Reward-guided policy update: scores samples.
- Fresh policy samples → Reward-guided policy update: sampled actions.
- Preference pairs → Policy/reference pairwise loss: offline DPO route.
- Policy/reference pairwise loss → Direct policy update: policy gradients.
Under Bradley–Terry preferences and KL-regularized reward optimization, . Rearranging expresses reward through a policy/reference log ratio plus a prompt-only constant. That constant cancels between responses, yielding DPO. The derivation requires reference support and does not guarantee equivalent finite-training outcomes.
Two valid three-outcome distributions expose the relative objective. Assume ; other responses are grouped into the third outcome. These are constructed distributions, not measured optimizer steps.
| Distribution | Chosen | Rejected | Other |
|---|---|---|---|
| Reference | 0.40 | 0.40 | 0.20 |
| Candidate policy | 0.30 | 0.20 | 0.50 |
The margin becomes . Loss falls from approximately 0.693 to 0.511, although chosen probability falls from 0.40 to 0.30. The chosen response gains relative to the rejected response, not necessarily in absolute probability.
margin = (logp_w - logref_w) - (logp_l - logref_l)
loss = -logsigmoid(beta * margin).mean()A simpler training path retains dependence on pair meaning and coverage. It can also optimize unintended correlates: tested DPO recipes expanded response length beyond the training distribution. Removing a reward network does not remove proxy error.
Composing a post-training recipe
| Available signal | Suitable operation | Required judgment |
|---|---|---|
| Reliable target responses | SFT | Which behavior should be imitated. |
| Meaningful response comparisons | Preference optimization | Which differences the rubric should favor. |
| Useful sampled-output scores | Reinforcement learning | Whether better scores represent better outcomes. |
These operations need not form one compulsory sequence. R1-Zero applied RL without initial SFT; R1 used cold-start demonstrations, reasoning RL, filtered-response SFT, and later RL. The distinction concerns particular recipes, not evidence that either route is universally preferable.
A cold start supplies examples of behavior that later reward optimization needs to discover. When a small model fails to learn an RL task, missing related SFT coverage is one diagnosis to test alongside task difficulty. Reintroducing demonstrations is an experiment, not a guaranteed repair.
Rejection-sampling fine-tuning generates candidates, retains selected responses, and applies supervised likelihood training to them. Filtering changes the dataset; it does not turn the student's update into a policy gradient. Distillation addresses transfer from teachers, and Synthetic Data addresses generated-example construction.
Reinforcement learning from AI feedback, or RLAIF, identifies the feedback source. Constitutional AI used model critiques and revisions for supervised training, then AI comparisons to fit a preference model for RL. Human choices remained in its principles and design. Choosing AI rather than human judgments does not choose the optimizer or supply independent ground truth.
Composed stages also appear in LFM2.5-1.2B: its Base checkpoint is distinguished from an Instruct checkpoint trained with SFT, preference alignment, and multistage RL. Record the parent checkpoint, operation, data version, candidate source, rubric, reward version, and resulting checkpoint so that a recipe describes reproducible changes rather than only a model name.
Proxy optimization and reward failures
A proxy is a measurable substitute for the intended goal. Reward hacking exploits weaknesses in that substitute; reward overoptimization occurs when stronger optimization improves proxy scores while degrading independently assessed quality. Goodhart's law frames the risk: targeting a measure can weaken its relationship to the original goal.
Optimization changes which errors matter. Best-of-N selects the highest proxy-scored response among N samples without updating the generator. More candidates can expose rare scoring mistakes. In controlled synthetic experiments, stronger selection or PPO eventually reduced a larger model's independent scores while pursuing a smaller proxy model. That larger scorer was an experimental comparator, not human welfare.
Accepted shortcuts can fail the task
ExampleOptimization can exploit the gap between acceptance and correctness.
Read the diagram as text
- Correct, faster computation.
- Incomplete reward checks.
- Reward optimization.
- Accepted no-op kernel.
- Proxy success.
- Independent computation check.
- Task failure.
- Correct, faster computation → Incomplete reward checks: imperfect translation.
- Incomplete reward checks → Reward optimization: supplies scores.
- Reward optimization → Accepted no-op kernel: reinforces shortcut.
- Accepted no-op kernel → Proxy success: accepted by proxy.
- Accepted no-op kernel → Independent computation check: executes on test inputs.
- Independent computation check → Task failure: required result absent.
Kernel-generation training exposed shortcuts including no-op kernels and returning reference code. Inspecting rollouts led to exploit detection, static checks that kernels existed and launched, and correctness and speed comparisons. These checks address different failure modes: source structure alone establishes neither correct execution nor speed.
Sycophancy favors agreement with a user's stated beliefs over truthful response. Preference research found that persuasive agreement could receive approval despite incorrectness. Optimization can amplify that mismatch. Separately, DPO length experiments show that implicit preference objectives can expand verbosity; longer answers are not inherently worse, but length must not stand in for the desired quality.
- Repair the acceptance rule — Check substantive requirements, not only easy surface constraints. More optimization cannot repair an omitted requirement.
- Test under optimization — Small training runs and inspected traces can reveal exploits absent from initial examples. Preserve discovered failures for future checks.
- Constrain movement — Clipping limits a local incentive. It does not establish that the rewarded direction is desirable.
Behavioral gains and competing requirements
Abstention declines to answer when support is insufficient. Rewarding it above a wrong answer can discourage fabrication, but fewer wrong answers may simply reflect fewer answers. Report accuracy among answered requests alongside answer coverage. Selective automation explains why both matter.
| Constructed assistant case | Desired response | Separate failure to track |
|---|---|---|
| Answerable legitimate request | Supported, useful completion | Incorrect answer or unnecessary refusal |
| Necessary evidence unavailable | Explicit uncertainty or abstention | Unsupported confident answer |
| Request prohibited by the specification | Appropriate refusal | Harmful compliance |
Over-refusal means refusing a safe request. XSTest pairs safe prompts with nearby unsafe contrasts to distinguish contextual judgment from reactions to vocabulary. Compliance means attempting an answer, regardless of accuracy. Testing only safe requests would also reward a system that answers everything, including prohibited requests.
Catastrophic forgetting is substantial loss of previously available capabilities after further training. Specialization gains and retained competence need separate measurements. Instruction-fine-tuning studies show that their balance depends on data, duration, and update configuration; no single adaptation method wins every comparison. Continual Learning develops retention methods.
A behavioral requirement should not be reduced to a surface style. If comparisons reward agreeable wording, favoring those labels does not repair factual support. If safe and unsafe cases share vocabulary, broadly rewarding caution can suppress legitimate assistance. Contextual examples and corrected judgments target these signal defects; tighter parameter constraints alone do not change label meaning.
Other dimensions remain distinct. Repetition measures whether generation loops, not whether it solves the task. Resource use measures expenditure, not competence. Where varied responses matter, define useful diversity explicitly rather than treating randomness as success. Separate metrics and meaningful task slices keep aggregate improvements from concealing losses.
Evidence of adaptation gains
Compare checkpoints on matched independent cases, recording prompts, decoding, answer limits, selection procedures, tool configuration, and evaluator versions. Account for prompt and output length when measuring resources. Controlled offline comparisons separates matched tasks from identical trajectories; a different route to success need not be a failure.
| Checkpoint comparison | Training difference | Evidence to keep separate |
|---|---|---|
| Starting model → SFT | Demonstration training | Target-task gains and retained capabilities |
| SFT → preference candidate | Comparison-based adaptation | Preference wins, factual quality, and response length |
| Starting policy → reward candidate | Sampled reward optimization | Training reward and independently assessed outcomes |
Contamination includes semantic leakage. Training on paraphrases or translations can inflate benchmark results while evading literal overlap checks. Teacher-generated examples are not automatically independent of public tests. Track lineage, investigate similar problems, and protect final assessment cases. Data used to select a recipe has become development data; see Independent data boundaries.
A score increase can reflect better task solving, formatting, selection, or more inference expenditure. In summarization research, controlling length reduced the measured preference advantage. A FinQA talk reported that simpler training outperformed mixed and progressive curricula, interpreting transfer as improved tool discipline; incomplete controls prevent treating that explanation as isolated causation.
Targeted ablations change one training component while preserving comparison conditions. Diagnostic rubrics can identify missing behaviors and guide new training data without becoming the scalar RL reward themselves. This separates learning where the failure occurs from deciding how to optimize it.
Report uncertainty in paired checkpoint differences, not only separate point estimates. Paired bootstrap resampling retains each case's model-to-model relationship; correlated cases require an appropriate sampling unit. Training-seed variation is a separate source of uncertainty. Uncertainty in scores and Release decisions connect these estimates to acceptance.
Boundaries of an alignment claim
A bounded report could state: Checkpoint {candidate_id}, compared with {baseline_id}, improved supported completion by {difference and interval} across {N} independent requests from {population}, under {prompt, decoding, and budget}. Unsupported answers, harmful compliance, benign refusals, and retention were assessed against {rubric_version}; {unmet criteria and exclusions} remain. These placeholders require observations, not inferred success from training loss.
| Claim | Necessary evidence | Unsupported extension |
|---|---|---|
| Preferred responses | Judgments under a specified comparison rubric | Universal correctness or benefit |
| Better task capability | Independent outcomes with contamination controls | Performance on every new distribution |
| Faithful explanations | Tests of whether explanations reflect influential factors | Access to internal motives from plausible prose |
| Resistance to tested attacks | Specified attack cases and observed behavior | Universal resistance to stronger attacks |
Checkpoint, prompt, tool, rubric, population, or operating-condition changes alter the claim's scope and may require reassessment. Even a system-prompt edit can shift behavior away from the fine-tuning distribution. Preserve the evidence-to-version relationship through Evaluation records and reassessment.
Trained behavior does not replace enforced permissions. Learning to disregard conflicting instructions can improve measured resistance while leaving vulnerabilities and benign-task regressions. Control placement and defense in depth explains enforcement; Adversarial tests and bounded security claims explains what attack testing establishes.
Open questions
Preference aggregation remains difficult when legitimate rubrics conflict. A scalar ranking cannot represent every majority cycle, and disagreement is not necessarily annotation error. Progress would preserve judgment provenance and demonstrate which populations benefit or lose under an explicit aggregation rule.
Long-trajectory credit assignment must distinguish useful actions from accidental companions of success. Shared terminal returns blur that distinction. Progress would show that localized feedback improves independent outcomes on alternative trajectories, with downstream states recomputed after changed actions.
Distinguishing capability elicitation from new capability learning requires more than higher scores. Rare pre-existing solutions can become easier to sample. Progress would compare strong starting-policy elicitation and sampling baselines against adaptation on genuinely new task families under matched budgets.
Reward validity under stronger optimization remains unresolved because new policies can discover previously unseen exploits. Progress would sustain independent task quality as optimization pressure increases, while testing fresh failure classes rather than only repairing known hacks.
























































































































