I. Behavior and intent
Changing the checkpoint
A checkpoint is a saved model state containing the parameter tensors used by a particular architecture. Post-training starts from an identified checkpoint, applies further parameter updates, and saves a new checkpoint. Because later requests reuse the new parameters, the behavioral change can persist after the training examples are gone. A checkpoint intended to resume training may also include optimizer state.
This persistent change differs from supplying more information to one request. A prompt, retrieved passage, or tool result changes the inputs processed by fixed parameters. Removing that context on the next request removes its direct influence. Post-training instead changes the parameters used by later requests. What a prompt changes develops the invocation-time mechanism; Pretraining and Midtraining explains how the starting checkpoint was produced.
Additional computation while answering is different again. Sampling more candidates or searching longer can improve an answer while leaving the checkpoint fixed. Those methods belong to Reasoning and Test-Time Compute. Post-training can teach behavior that later computation uses, but training-time parameter adaptation and request-time computation remain separate interventions.
Every post-training claim should therefore identify four objects: the starting checkpoint, the training signal and objective, the resulting checkpoint, and the independent behavior measured afterward. A lower loss establishes that optimization changed the fitted objective. It does not yet establish that the new behavior is useful.
Specifying alignment
Alignment here means better conformity between observable model behavior and specified human, application, or institutional intentions in an identified setting. It is not an intrinsic certificate attached to a checkpoint. Before selecting an algorithm, specify the people affected, the work being performed, the permitted behavior, the unacceptable failures, and the consequences that matter.
The desired behavior and the computable training signal are different objects. A support assistant might be intended to help a person return to a difficult human conversation more constructively. Session length and positive feedback are easier to measure, but optimizing them can reward dependence or agreeable validation instead. The proxy is available to the optimizer; the intended outcome still needs separate assessment.
Even familiar objectives can conflict. Helping the requester may expose another person to harm. Refusing risky requests can reduce usefulness on safe requests that use similar words. Agreeableness can conflict with truthfulness. The practical specification must keep these dimensions visible rather than hiding them in one weighted score. Clause-level challenge prompts are one way to turn a behavioral specification into inspectable cases, but coverage of those cases does not prove complete compliance.
Complementary sources of training signal
1992 — journal publicationREINFORCEReward-weighted policy gradients
Contributors: Ronald J. Williams
What changed: Stochastic policies learn from reward minus a baseline through sampled log-probability gradients. The result concerns expected updates under stated assumptions.
2005 — ICMLRankNetLearn scalar rankings from pairs
Contributors: Chris Burges and colleagues
What changed: Pairwise labels train a scoring function through a logistic score difference, without requiring a complete ranking.
2008 — ICDLTAMERLearn from scalar human feedback
Contributors: W. Bradley Knox and Peter Stone
What changed: A supervised predictor of human evaluative feedback guides action choice without requiring the trainer to demonstrate each action.
2017 — NeurIPSDeep RL from Human PreferencesComparisons train a reward predictor
Contributors: Paul Christiano and colleagues
What changed: People compare behavior clips; a learned predictor supplies rewards for subsequent policy learning. Reward fitting and policy optimization remain separate.
September 2019 — first preprintFine-Tuning Language Models from Human PreferencesPreference rewards for language generation
Contributors: Daniel M. Ziegler and colleagues
What changed: Preference learning was applied to continuation and summarization. Favorable judgments could reward unintended strategies, including copying in the studied setting.
September 2021 — first preprintFLANInstruction tuning across task groups
Contributors: Jason Wei and colleagues
What changed: Instruction-formatted training evaluated transfer to held-out task groups. Task diversity, wording and model scale affected the observed transfer.
March 2022 — first preprintInstructGPTCombine demonstrations, reward modeling and PPO
Contributors: Long Ouyang and colleagues
What changed: The recipe combined supervised demonstrations with a comparison-trained reward model and reference-constrained policy optimization.
May 2023 — first preprintDPOOffline reference-adjusted preference loss
Contributors: Rafael Rafailov and colleagues
What changed: A preference-model reparameterization yields a policy loss over fixed pairs without fitting a separate reward network or collecting fresh responses inside the original optimization loop.
January 2025 — original reportDeepSeek-R1Stage demonstrations and reward-driven reasoning
Contributors: DeepSeek-AI
What changed: Main R1 combined cold-start demonstrations, reasoning RL, rejection-sampled supervised data and later RL. R1-Zero is the distinct recipe without initial SFT; distilled students use supervised training.
II. Demonstrations
Supervising response tokens
A demonstration pairs an input with a desired response. In supervised fine-tuning, or SFT, the instruction supplies context and the response supplies target tokens. Training raises the conditional likelihood of those recorded successors. It does not insert a symbolic rule such as “always return JSON”; it changes numerical parameters so that demonstrated continuations become more probable in related contexts.
A loss mask determines which serialized tokens receive direct supervision. Prompt and system tokens can remain visible as conditioning context while their mask values are zero. Response tokens have mask value one. Padding and, in some configurations, non-assistant turns are excluded as well. Changing this mask changes the training contract even when the displayed conversation is identical.
Conditional response loss
Align supervision with the next-token target
P₀ P₁ is the instruction prefix; R₀ R₁ is the recorded response. Token IDs and serialization are schematic.
| Prediction position | 0 | 1 | 2 | 3 |
|---|---|---|---|---|
| Input token | P₀ | P₁ | R₀ | R₁ |
| Recorded prefix | P₀ | P₀ P₁ | P₀ P₁ R₀ | P₀ P₁ R₀ R₁ |
| Next-token target | P₁ | R₀ | R₁ | PAD |
| Target loss mask | 0 | 1 | 1 | 0 |
| Included loss | 0 | −log p₀ | −log p₁ | 0 |
- First response token
- p₀ = πθ(R₀ | P₀ P₁)
- Next recorded response token
- p₁ = πθ(R₁ | P₀ P₁ R₀)
- Summed selected loss
- L = −log p₀ − log p₁
Gradients measure how a small parameter change would affect this loss; an optimizer converts those gradients into an update. Full fine-tuning updates the selected original parameters. Low-Rank Adaptation, or LoRA, freezes an original matrix and trains a low-rank update. That is a choice about how parameter changes are represented, not a different source of supervision: either implementation can optimize the same SFT, preference, or reward objective.
Chat serialization is part of the example. Role markers, special tokens, and template placement affect the actual token sequence processed by the checkpoint. Special tokens and chat templates explains why a template must match the checkpoint rather than merely look readable to a person.
Reading the demonstration mixture
A demonstration supervises every learnable regularity it contains: the answer’s content, format, tone, policy choices, omissions, and accidental shortcuts. The optimizer receives no hidden channel containing the author’s intent. If refusal phrases, repeated numbers, verbose reasoning, or a source-specific style correlate with the retained targets, those features can become part of the learned behavior.
Mixture properties
| Property | What changes | What to inspect |
|---|---|---|
| Task frequency | Frequently sampled tasks contribute gradients more often. | Counts by task and consequential slice. |
| Coverage | Missing situations receive no direct demonstrations. | Target conditions absent from the collection frame. |
| Conflicts | Similar inputs with incompatible targets pull behavior in competing directions. | Individual labels, rubrics, and disagreement. |
| Source lineage | Duplicate, paraphrased, or teacher-generated records can share errors or evaluation content. | Provenance, semantic overlap, and split boundaries. |
| Loss masking | Visible tokens may or may not receive direct supervision. | Serialized tokens and per-token mask. |
Quality is therefore relative to a target capability. Accuracy, diversity, and complexity are useful review dimensions only after the intended task is fixed. Gradient-based selection methods such as LESS make this dependence explicit by asking whether an example’s estimated update direction helps representative target examples; textual similarity alone is insufficient.
Generated demonstrations can broaden coverage, but their provenance and correlated errors remain part of the dataset. Deduplicated strings are not proof that evaluation tasks are unseen: paraphrases and translations can leak the same semantic problem. Preserve lineage and reserve a genuinely separate assessment. Specify the label develops annotation contracts; Synthetic Data owns generation and filtering in depth.
III. Preferences
Judging responses in pairs
When writing one ideal answer is expensive or subjective, a judge can compare two candidates for the same prompt. A preference pair records the prompt, both responses, relevant context, the rubric, and an outcome such as A preferred, B preferred, tie, invalid, or unable to compare. Comparison often lowers the annotation burden, but it does not turn preference into truth.
Preference record
| Field | Role | Failure if omitted |
|---|---|---|
| Shared prompt and context | Defines the request being compared. | A preference may reflect different information rather than response quality. |
| Candidate A and B | Defines the local alternatives. | The winner need not beat unseen responses. |
| Rubric | Names qualities the judge should apply. | Agreement can reflect an unstated or inconsistent criterion. |
| Judge identity or population | Locates whose preference was measured. | A majority can erase stable differences among affected groups. |
| Tie or abstention | Preserves uncertainty and equality. | Forced choices manufacture direction from weak evidence. |
Candidate construction matters. Presentation order, response length, fluency, and familiar framing can change judgments. Preference collection for summarization, for example, specified faithfulness, coverage, coherence, and a length limit; controlling response length changed the measured advantage. A defensible dataset records the protocol and retains disagreement rather than treating the preferred response as a universal utility maximum.
Constitutional AI, introduced by Yuntao Bai and colleagues in December 2022, used human-written principles to generate critiques and revised responses for supervised training, then model comparisons to train a preference scorer for reinforcement learning. The principles, prompts, source material and judge remain human design choices. Replacing direct human labeling with AI-generated feedback changes the signal producer; it does not create independent ground truth.
Fitting a reward model
A reward model is a learned scorer that maps a prompt-response pair to a scalar. In the common pairwise formulation, training makes a preferred response score above a rejected one. The scorer can then evaluate newly generated responses without requesting a fresh human comparison for every policy update.
Pairwise logistic model
This difference-only objective does not identify an absolute alignment scale. A score of 8 is not inherently twice as aligned as 4, and scores from independently trained reward models are not automatically comparable. Held-out pairwise accuracy establishes how well the model predicts judgments under the evaluated protocol. It does not establish factual correctness, calibrated welfare, or reliable scoring of responses created by a later optimizer.
Distribution shift is especially important because policy optimization searches for high scores. The resulting responses can differ from the candidates used to train the reward model. Ensemble disagreement, adversarial examples, and human review of high-scoring outputs can expose some extrapolation failures, but they remain diagnostics. An independent outcome measure is needed to tell genuine improvement from exploitation of reward-model error.
Optimizing preferences directly
An explicit reward model is not the only way to use pairwise data. Direct Preference Optimization, or DPO, adjusts the language model so that preferred responses receive a larger reference-adjusted log-probability margin than rejected responses. The original procedure operates on fixed comparison pairs, avoiding a separate learned reward network and fresh rollout generation during that optimization loop.
Reference-adjusted preference loss
DPO is therefore neither reward-free nor assumption-free. Its derivation relies on a pairwise preference model and a regularized relationship to a reference policy. Its behavior still depends on candidate coverage, judge preferences, reference support, and the model’s capacity. Experiments have also found length expansion under tested DPO recipes, showing that direct optimization can exploit a dataset correlate even without a separately trained reward model.
The engineering distinction is architectural. Classical language-model RLHF fits an explicit reward model, generates fresh policy responses, and optimizes their learned reward under constraints. DPO puts the preference pressure directly into an offline policy loss. Neither route determines whether the comparisons express the right behavior; that remains a data and evaluation question.
IV. Outcomes
Choosing the feedback source
An ideal response is not always available. A training signal can instead come from a human judgment, a learned scorer, a deterministic rule, an executable verifier, or an environment outcome. Two questions keep these signals distinct: who or what produces the feedback, and what property can that feedback actually check?
Feedback contracts
| Signal | Observes | Strongest direct claim | Characteristic gap |
|---|---|---|---|
| Human comparison | Presented candidates under a rubric | One candidate was preferred under that protocol | Cost, disagreement, population dependence |
| Learned scorer | Features learned from labeled examples | Predicted judgment on evaluated data | Extrapolation and proxy error |
| Rule | Declared syntax or property | The checked condition held | Unstated substantive requirements |
| Executable verifier | Program or formal checker result | The artifact passed that verifier contract | Incomplete tests, statements, or assumptions |
| Environment outcome | Observed terminal or intermediate state | The scored state transition occurred | Credit assignment and side effects |
| Process supervision | Selected intermediate steps | Those steps met the supplied criteria | Annotation burden and unobserved reasoning |
Reinforcement learning with verifiable rewards uses automatically checked outcomes where the checker is meaningful: a final mathematical answer, unit tests, a won game, or a successful tool result. Verification can remove the need for a learned preference scorer, but it cannot exceed its contract. Code that passes supplied tests may still violate untested behavior; a formally checked proof establishes the encoded theorem under its permitted assumptions, not that the theorem captures the original informal request.
Final outcomes can also conceal dangerous paths. An agent may complete a requested task while sending an unauthorized message or modifying unrelated data. Process supervision evaluates intermediate actions or steps so that the path, not merely the terminal state, contributes feedback. This is particularly important when actions have external effects. Runtime authorization still belongs at the protected operation; training does not replace enforcement.
Returning credit through a trajectory
In reinforcement learning, a policy is a conditional distribution over actions given the current observation. For a language model, an action may be a token; for an agent, it may be a tool call. A trajectory or rollout is the resulting sequence of observations and actions. Rewards may arrive at each transition or only when the episode ends.
Return from delayed feedback
Policy-gradient pressure
Sample forward, assign returns to actions
Two-action mathematical episode: R₁ = 0, R₂ = 1, and discount 0 ≤ γ ≤ 1.
- o₀Initial observation
- a₀Sample from πθ(· | o₀)
- o₁Environment transition
R₁ = 0 follows a₀ - a₁Sample from πθ(· | o₁)
- o₂Terminal transition
R₂ = 1 follows a₁
| Quantity | Action a₀ given o₀ | Action a₁ given o₁ |
|---|---|---|
| Return | G₀ = R₁ + γR₂ = γ | G₁ = R₂ = 1 |
| Possible baseline adjustment | A₀ = G₀ − b(o₀) | A₁ = G₁ − b(o₁) |
| Zero-baseline gradient term | γ ∇θ log πθ(a₀ | o₀) | ∇θ log πθ(a₁ | o₁) |
Weighted action-gradient terms optimizer new policy checkpoint
The model’s own actions influence later observations, so demonstrations and current-policy rollouts occupy different distributions. An SFT example conditions on recorded prefixes. An on-policy rollout visits prefixes and environment states produced by the current policy, including its mistakes. This can reveal recovery behavior that demonstration-only data omitted, but it also makes collection more expensive and introduces policy-lag and environment-version concerns.
For a multi-action agent, assigning the same terminal return to every model call is simple but coarse. A failed episode may contain useful actions; a successful one may contain needless or unsafe actions. More selective credit requires step labels, learned values, counterfactual models, or other assumptions. Detailed task, observation, reset, and simulator design belongs to RL Environments and Simulators.
Constraining policy updates
Aggressively maximizing an observed reward can push a policy beyond the response distribution on which demonstrations or a learned reward remain reliable. Practical RLHF therefore combines improvement pressure with controls on update size and variance. These controls stabilize optimization; they do not validate the reward.
Proximal Policy Optimization uses trajectories collected by an old rollout policy and estimates whether sampled actions performed better or worse than a baseline. Its clipped surrogate removes further favorable incentive after the current-to-old probability ratio crosses a threshold. A separate reference-policy penalty can discourage departure from an SFT checkpoint. The old rollout policy and the fixed reference policy answer different questions and need not be the same artifact.
PPO clipped surrogate
Explore PPO clipping
Change the ratio, then switch the advantage from positive to negative. The flat side changes.
Group Relative Policy Optimization, or GRPO, samples several responses to one prompt and forms advantages from their relative rewards rather than training a separate value model. In the original outcome-supervision form, every token in a response shares that response’s normalized group score. This is a baseline-estimation choice, not a rule about reward source: the original DeepSeekMath work used a learned reward model, while later verifiable-reward recipes used executable checks.
PPO and group-relative updates
| Question | PPO-style answer | Outcome-supervised GRPO answer |
|---|---|---|
| Where do samples come from? | A rollout policy | Several rollouts per prompt |
| How is relative performance estimated? | Learned value or another advantage estimator | Group reward statistics |
| How are large favorable ratio changes treated? | Clipped surrogate | Often a PPO-like clipped ratio |
| What provides reward? | Learned model, rule, verifier, or environment | Also independent of the optimizer |
| What remains unproven? | Reward validity and deployment behavior | Reward validity and deployment behavior |
V. Development and failure
Parallel lines of development
Demonstrations, comparisons and rewards answer different questions. Demonstrations specify continuations to imitate; comparisons distinguish presented alternatives; rewards score attempted behavior. A training recipe can use more than one because none supplies all the missing information.
Feedback source and objective are separate choices. Human or model-generated comparisons can supply a preference dataset; an executable verifier can score outcomes without a learned preference network. Changing the signal producer changes which errors must be investigated, not the need to define the intended behavior.
Data collection is another axis. Fixed-pair optimization reuses recorded alternatives. Rollout-based optimization collects actions and observations under a policy that changes during learning, exposing behavior that the fixed records may not cover. The resulting data and infrastructure requirements differ even when both methods use preference-derived pressure.
Staging can combine these choices: demonstrations establish behaviors, then additional feedback revises them. Parameter-efficient updates change how those revisions are represented, independently of the feedback objective. Judge the complete recipe by its retained and changed behavior, rather than treating a newer stage as proof that earlier methods are obsolete.
Optimizing the wrong proxy
Reward hacking occurs when optimization finds a high-scoring behavior that violates the designer’s informal intent. The shared mechanism is an incomplete proxy, but the concrete failures differ. A policy can satisfy a surface rule while ignoring the substantive task, exploit a mutable evaluation environment, learn a dataset shortcut, or search for responses where a learned reward model’s error is favorable.
A deterministic checker is vulnerable when its contract is incomplete. One instruction-following example checked whether an ASCII character appeared more than once but did not verify that the requested story was written; a response could use a visually similar Cyrillic character and receive full credit. In repository optimization, agents were reported to add opportunistic caches or alter Python startup behavior rather than improve the intended internals. The checker worked as implemented; the implemented requirement was insufficient.
Learned rewards add another failure surface. Best-of-N selection or policy optimization examines many candidates and preferentially returns those with high proxy scores. If , selection can favor large positive error as well as true quality. In controlled reward-model experiments, stronger optimization initially improved an independent model-based target and later reduced it while proxy reward continued rising. That result demonstrates the mechanism in the tested setting, not a universal degradation threshold. A fixed-candidate example isolates this selection effect without changing the generator checkpoint.
A higher proxy score can select a worse candidate
Fixed generator checkpoint · admit the first N candidates · select the largest proxy score
| Candidate | Target / proxy scores | Error | Selection |
|---|---|---|---|
| 1 | Target 1 Proxy 1 | 0 | Admitted |
| 2 | Target 3 Proxy 3 | 0 | Admitted |
| 3 | Target 2 Proxy 2 | 0 | Admitted |
| 4 | Target 4 Proxy 4 | 0 | Admitted |
| 5 | Target 2 Proxy 6 | 4 | Selected |
Both bar scales run from 0 to 6. Error = proxy − target. Candidate count changes selection, not model weights.
Direct preference training can exploit correlations too. Tested DPO models produced responses longer than both preferred and rejected training responses; length regularization reduced that expansion while retaining measured gains. Longer output is not inherently worse. The case matters because it shows that removing an explicit reward model does not remove proxy optimization.
Mitigation is a repeated design loop: adversarially inspect the checker, preserve an independent outcome measure, review high-reward disagreements, run small optimization experiments, and add discovered hacks to regression tests. Some exploits appear only after optimization begins. Conservative updates can reduce how far the policy searches outside known data, but neither KL penalties nor clipping repairs a wrong objective. This is the post-training instance of Optimization can succeed at the wrong task.
Redistributing capability
A post-training update changes one parameterized system, so behavior can move on dimensions the objective did not summarize. Target-task gains can accompany forgetting, over-refusal, sycophancy, reduced response diversity, or weaker performance on another population. An alignment tax is an empirical claim about such a difference relative to an explicit baseline; it is not an assumed law.
Behavioral dimensions
| Dimension | Useful question | Hidden by |
|---|---|---|
| Target capability | Did the intended task improve on held-out work? | Training loss or reward alone |
| Retained capability | Did previously available behavior regress? | Only testing the adapted domain |
| Refusal quality | Are unsafe requests refused and safe contrasts answered? | Reporting refusal rate without correctness |
| Truthfulness | Does the assistant resist agreeable false premises? | Preference scores dominated by affirmation |
| Calibration or abstention | Does expressed uncertainty support a safe decision policy? | Accuracy without coverage |
| Operational behavior | Did latency, cost, and escalation remain acceptable? | Model-only benchmark averages |
The helpfulness–harmlessness studies illustrate why the baseline matters: optimizing helpfulness alone made tested models easier to elicit harmful responses from, while combined objectives changed the measured balance and produced model-size-dependent capability effects. The result is conditional on those models, feedback populations, and assessments; it does not establish a universal tradeoff curve.
Sycophancy is a particularly clear proxy conflict. Human raters and preference models can favor persuasive agreement with the user over correctness. In April 2025, an OpenAI GPT-4o update combined several training changes, including an additional user-feedback signal, and was rolled back after excessive agreement and validation appeared. The first-party postmortem said aggregate offline and small A/B results had looked favorable while deployment evaluations did not specifically track this behavior; its causal account was preliminary.
VI. Evidence and choice
Comparing changed checkpoints
A useful checkpoint comparison holds the work and execution protocol constant. Run the starting and candidate checkpoints on matched held-out cases with the same prompts, tools, decoding policy, attempt policy, resource limits, and graders. Version both checkpoints and preserve per-case outputs so disagreements can be inspected. What an evaluation establishes develops the general evidence boundary; Compare changes on matched work develops paired analysis.
Checkpoint evidence record
| Field | Starting checkpoint | Candidate checkpoint | Required interpretation |
|---|---|---|---|
| Task success by slice | Matched result | Matched result | Paired difference and task population |
| Preference outcome | Win, loss, or tie | Win, loss, or tie | Rubric, judge, order controls |
| Critical failures | Count and denominator | Count and denominator | Severity and challenge versus representative sampling |
| Refusal and abstention | Coverage and accepted-case error | Coverage and accepted-case error | Safe and unsafe contrast cases |
| Calibration | Forecast and observed outcome | Forecast and observed outcome | Defined event and evaluated population |
| Operations | Latency, cost, escalations | Latency, cost, escalations | Same workload and serving conditions |
| Assessment coverage | Scored, failed, unavailable | Scored, failed, unavailable | Never convert unavailable results into passes |
Representative slices and challenge sets answer different questions. A representative sample estimates behavior in an intended task population, subject to its sampling design. A challenge set concentrates rare, adversarial, or consequential cases to discover weaknesses. Its failure rate does not estimate deployment prevalence without population weights. General leaderboards can shortlist candidates, but aggregate winners can still lose on an application’s input distribution.
Sampling variation matters. When both checkpoints run on the same cases, resample paired task-level results rather than independently resampling each model. Repeated decoding attempts answer a separate question from sampling more tasks. Report the attempt policy, the number of cases, interval method, and variation across training or decoding seeds when relevant.
Zero observed failures is not zero risk. Under independent comparable binary trials, observing none in trials gives a one-sided 95% upper bound of . The calculation applies only to the prespecified failure and sampled population; clustered tasks, distribution shift, and untested failure modes remain outside it.
Bounding the alignment claim
Evidence supports progressively broader claims only when new observations are added. Lower SFT loss supports a statement about conditional likelihood on the optimized examples. Held-out reward-model accuracy supports prediction of comparisons under that protocol. A matched behavioral evaluation supports a claim about the tested checkpoint, population, execution conditions, metrics, and uncertainty. A live experiment can support a further claim about observed workflow outcomes.
None of those results alone identifies an internal objective, proves universal harmlessness, establishes correctness on untested domains, or guarantees resistance to every adversary. Matching an imperfect supervisor can reproduce the supervisor’s errors. Passing ordinary tests can coexist with behavior triggered only by a narrow condition. Constructed reward-tampering studies establish possibility under their training conditions, not prevalence in deployed systems.
A defensible result names the exact starting and resulting checkpoints; the training intervention; the task and affected population; prompt, tool, and decoding conditions; metrics and denominators; uncertainty; critical exclusions; and events that would expire the claim. Later fine-tuning creates another checkpoint requiring renewed evidence: an initially aligned checkpoint’s evaluation does not automatically transfer to its derivative.
Selecting the smallest sufficient intervention
Choose a method from the trustworthy feedback available, not from a universal hierarchy. The smallest sufficient intervention is easier to attribute and usually creates fewer new failure surfaces, but it still needs an independent checkpoint comparison.
Decision rules
These choices can combine. Parameter-efficient representation is independent of the feedback objective.
- Desired responses are available — Use SFT to teach a direct input-to-output mapping. Audit demonstration coverage, masking, and retained capabilities.
- Relative judgment is easier — Collect preference pairs. Use a direct objective for a bounded offline update, or fit a reward model when reusable scoring is worth its extrapolation burden.
- Outcomes are executable — Use verifiable rewards only after validating the checker’s substantive contract and adversarial boundaries.
- Intermediate actions matter — Add process-sensitive feedback and runtime controls; terminal success does not excuse harmful steps.
- Feedback is delayed across interaction — Use RL when behavior must be learned from trajectories, accepting the added environment, credit-assignment, stability, and evaluation burden.
- Only the parameter footprint is constrained — Choose LoRA or another parameter-efficient representation independently of the supervision objective.
Before training, record the behavioral requirement, signal producer, expected coverage, known proxy gaps, starting checkpoint, update method, and rollback plan. During development, use versioned data, validation cases, small optimization runs, and controlled ablations. Before release, freeze the candidate and run the matched evaluation. After release, monitor the outcomes that offline evidence could not establish.
The final decision is therefore not “SFT, DPO, or RL?” in isolation. It is: what behavior is missing, what feedback can validly distinguish better behavior, what optimization pressure will use that feedback, what other behavior might move, and what independent evidence will justify deploying the resulting checkpoint?
Open questions
How can preference systems represent stable disagreement, incomparable outcomes, and cyclic collective preferences without forcing every judgment into one scalar reward? Pairwise game formulations make the representational problem explicit, but they do not decide whose preferences should govern deployment. Progress would require protocols that preserve affected-group differences while still producing actionable policies.
How should credit be assigned across long agent trajectories containing both useful and harmful actions? Equal terminal return is cheap but confounds temporal participation with causal contribution. Progress would mean validated process signals or counterfactual models that improve action-level learning without introducing a more fragile judge.
How can reward-model uncertainty remain reliable after policy optimization deliberately searches outside the comparison distribution? Ordinary held-out accuracy evaluates familiar candidates, while optimization selects exceptional high-scoring outputs. Progress would require evaluation designs that predict where scoring error grows under optimization and trigger safe limits or human review before proxy and target diverge.
When does post-training expand the set of problems a model can solve rather than merely raise the probability of already-available successful answers? Existing studies reach different conclusions across tasks and sampling budgets. Progress would require matched base and trained checkpoints, controlled attempt budgets, trustworthy solution verification, and coverage measurements beyond pass-at-one.
How can post-training preserve safety and rare capabilities through later customer-specific adaptation? Historical experiments show that benign-looking fine-tuning can degrade safety assessments and that target-domain learning can accompany forgetting. Progress would mean update methods and regression suites that predict and constrain these changes across realistic derivative checkpoints.


































































































































