“Fine-tuning” is not one single recipe. This chapter maps the main approaches so you can name what you are doing and why.
| Approach | Plain-English idea |
|---|---|
| Unsupervised fine-tuning | Continue training on domain text without instruction labels (domain language soak) |
| Supervised fine-tuning (SFT) | Train on input → desired output pairs |
| Safety / alignment fine-tuning | Extra training so the model follows policies and preferred behavior |
| Full fine-tuning | Almost every weight can update |
| PEFT | Train only a small part (adapters, LoRA, soft prompts, …) |
Feed lots of domain text (legal corpus, codebase, medical notes) so the model absorbs domain language. There may be no “instruction → answer” labels. Useful for domain familiarity; not the same as teaching a chat format.
You provide clear examples: given this input, produce that output. This is the workhorse for task adaptation and instruction-style models (next chapter goes deeper).
After (or alongside) capability training, you further shape the model so it is more helpful, honest, and policy-compliant. Methods vary (preference data, RL-style loops, and related recipes). For this fundamentals session, remember the goal: safer, more aligned behavior — not every algorithm detail.
Every (or almost every) weight can move.
Update only a small number of parameters (or add tiny modules / soft prompts).
PEFT families you will meet later in Module 3:
| Family | Idea in one line |
|---|---|
| Additive | Add small modules (adapters) |
| Selective | Train only some existing weights |
| Re-parameterization | Cheap update forms (LoRA / QLoRA) |
| Soft prompting | Learn virtual prompt tokens |
Use PEFT when you want most of the benefit of adaptation without paying full fine-tune cost.
Fine-tuning comes in flavors — unsupervised, supervised, alignment, full, or PEFT — pick by data type, cost, and how much of the model must change.