Preference Optimization

Preference optimization trains a model to prefer outputs that humans, users, tests, or another evaluator rank higher. It includes reward-model-based reinforcement learning and direct objectives over preference pairs.

For pairwise preference data , a common loss is:

Here is the preferred output, is the less preferred output, and is a reward or preference score.

Why It Matters

  • Aligns model behavior with goals that are hard to specify as a loss.
  • Common in the post-training stage of large generative models.
  • Quality depends heavily on the preference data and reward signal.

Direct Preference Objective

Direct Preference Optimization (DPO)-style objectives compare a policy to a reference model:

where anchors the optimized policy and controls how strongly the policy can move away from the reference.

Preference Data Contract

FieldQuestion
Prompt or taskWhat condition is the preference about?
Compared outputsAre outputs final answers, trajectories, code diffs, molecules, poses, or plans?
Preference sourcehuman, expert, model judge, verifier, benchmark, or rule?
Label typepairwise, ranking, scalar score, binary accept/reject, or edit preference?
Distributiongenerated by which policy or sampler?
Tie and ambiguity policyare equal or low-confidence preferences kept?
Safety/public boundarydoes the data contain private prompts, people, paths, or unpublished details?

Preference optimization is only as meaningful as the comparison protocol.

Evidence Boundary

ClaimRequired Evidence
better human preferenceheld-out preference evaluation with annotator or judge protocol
better task performancetask metric, execution result, verifier, or benchmark score
safer behavioradversarial or policy-specific safety evaluation
less reward hackingexamples where optimized score and external quality agree
stable post-trainingKL/reference drift, regression checks, and capability retention

Do not equate higher preference-model score with true quality unless external evaluation supports it.

Checks

  • Are preference labels consistent and free of annotator bias?
  • Does optimization reward-hack the proxy instead of the true objective?
  • How much does the policy drift from the reference model?
  • Is the preference signal collected from realistic tasks or artificial comparisons?
  • Does the evaluation use fresh prompts not used for preference collection?
  • Are win rates paired, confidence-bounded, and judged with a stated protocol?