POST-TRAINING & DISTILLATION

MODULE 4: PREFERENCE & ALIGNMENT · SCENE 10

The Bradley-Terry Preference Model

P(y_w ≻ y_l) = σ(r_w − r_l): the probability model underpinning RLHF and every preference-optimization method.

REWARD GAP r_w − r_lσ(gap) = 0.881LOSS = 0.127
P(y_w ≻ y_l) = σ(r_w − r_l)gap −5 … +7

Confident separation. Reward-model training pushes gaps up until held-out pairs are ranked correctly.

ARCHITECTURE & FORMULATIONModule 4: Preference & Alignment

Bradley-Terry: preferences as probabilities

Ask a human 'is A better than B?' and the answer is noisy. Bradley-Terry turns pairwise comparisons into a scalar reward per response, where the probability A wins is a sigmoid of the reward gap. It is the statistical foundation under RLHF, DPO, and every variant.

The Model

Each response gets a latent reward r. P(y_w ≻ y_l) = σ(r_w − r_l). Fit rewards by maximizing the likelihood of observed human choices.

The Loss

Reward-model training minimizes −log σ(r_w − r_l) over pairs. A well-fit model ranks held-out pairs correctly; its accuracy is the ceiling of everything downstream.

Why Pairs

Pairwise 'which is better' is far more reliable than absolute 1–10 scoring. Humans are consistent comparators, inconsistent scorers.

MATHEMATICAL FORMULATION · PREFERENCE LOSS
L_RM = −log σ(r_w − r_l) = −log P(y_w ≻ y_l)

Reward margin of 2.2 gives σ(2.2) ≈ 0.90 → loss 0.105. Margin 0 gives loss log 2 ≈ 0.693, the maximum a binary comparison can contribute.

REAL-WORLD PRODUCTION ENGINEERING
  • Reward-model accuracy on held-out pairs is typically 65–75% — every downstream RLHF run inherits that noise ceiling.
  • Annotator disagreement is data: many teams train an ensemble of reward models and treat disagreement as an uncertainty signal.
Agent-native web · research mode

Experimental WebMCP · evolving community-group draft, not a W3C Standard or on the Standards Track.

Native status: Initializing. Registered: none

DOM → inferred capabilities · WebMCP → declared capabilities. Tools read real CUDA/Inference Atlas content. Calls may highlight temporary UI state. No backend or remote telemetry.

Local harness verifies application logic; it does not demonstrate native discovery or a browser agent.

Input schema
{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 1,
      "maxLength": 300
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 10
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false
}

Local log: last 100 calls while this panel is open. Inputs may contain personal text; review before sharing.

[]