Chapters 1-3
Introduction to RLHF
A compact orientation to what RLHF changes, why the field formed, and how the modern training loop fits together.
Why post-training exists
Pretraining teaches broad world knowledge, but it does not by itself produce the style, reliability, and responsiveness people expect from assistants.
RLHF is the family of post-training methods that pushes a base model toward useful behavior by turning vague human judgments into a training signal.
The core mental move is simple: instead of asking only what token comes next, we also ask which completed answer is more helpful.
The field came from preference learning
Modern RLHF did not appear fully formed with chatbots. It grew out of earlier work on learning reward functions from human comparisons in ordinary RL.
The breakthrough in language models was realizing that the same comparison loop could supervise open-ended text, not only actions in a simulator.
That history matters because it explains why reward models, KL penalties, and asynchronous feedback pipelines still show up today.
The pipeline is not one algorithm
RLHF is a pipeline of stages: instruction tuning to get the model into the right interaction format, data collection to define good behavior, a reward signal to score generations, and an optimizer to push the policy toward those scores.
Different labs swap pieces in and out. Some use policy gradients, some use direct preference optimization, some rely heavily on rejection sampling or synthetic feedback.
The stable concept is not the exact recipe. It is the idea of translating human preferences into an objective that can shape model behavior.
Canonical recipes differ for a reason
InstructGPT, Tulu 3, and DeepSeek-style reasoning pipelines all share the same broad logic, but they emphasize different targets: assistant behavior, capability breadth, or reasoning performance.
This is why you should think in terms of tradeoffs instead of a single 'correct' RLHF stack.
Every later chapter is one lens on that same design space: what signal you optimize, where it comes from, and what you risk by trusting it.
Review
5 quick checks
Questions with revealed answers.
1 Why is pretraining alone usually not enough for a chat assistant?
Because pretraining optimizes next-token prediction on broad data, not the specific behaviors people want from an assistant such as instruction following, tone, and preference-sensitive helpfulness.
2 What is the core idea that unifies the RLHF pipeline?
Human judgments are turned into a usable training signal that can steer a language model after pretraining.
3 Why is it misleading to talk about RLHF as one fixed recipe?
Different systems use different combinations of instruction tuning, reward modeling, policy optimization, direct alignment, rejection sampling, and synthetic data. The stable part is the preference-driven post-training goal.
4 What role did earlier preference-learning work play?
It supplied the conceptual template for learning a reward proxy from comparisons and then optimizing behavior against that learned signal.
5 What should someone leave this page knowing before moving on?
That RLHF is best understood as a modular post-training pipeline for turning human preferences into better model behavior, not as a single algorithm.