Training, Alignment & Adaptation Datasheet — SOTA++ 2026¶
Inference starts at \(\theta\). This document explains how \(\theta\) got there: data, objectives, optimization, SFT, preference optimization, RL, PEFT, distillation, merging, pruning, and continual adaptation.
The conceptual boundary is:
The same backbone can produce radically different behavior depending on the dataset, objective, optimizer trajectory, and post-training.
See also:
- 01_GUT_GENERATIVE_AI_UNIFIED_ENGINEERING
- 02_LLM_TRANSFORMER_INFERENCE_DATASHEET
- 12_REWARD_VERIFIER_JUDGE_DATASHEET
- 17_EVALUATION_BENCHMARK_EXPERIMENTATION_DATASHEET
- 09_LOCAL_AI_INFERENCE_RUNTIME_DATASHEET
1. The complete training graph¶
A useful high-level view is:
raw data
↓
filter / license / quality / safety
↓
deduplicate / normalize / tokenize
↓
mixture construction / curriculum / packing
↓
PRETRAIN
↓
base model θ₀
↓
SFT / instruction tuning
↓
preference / reward / verifier training
↓
offline preference optimization or online RL
↓
distillation / PEFT / domain adaptation / merge
↓
checkpoint θ*
↓
quantization / runtime packaging
↓
inference
There is no single “training step.” There are multiple update operators applied at different stages.
2. The universal update equation¶
For parameters \(\theta\), loss \(\mathcal L\), and learning rate \(\eta\):
where \(u_t\) is the update direction produced by the optimizer from gradients and its state, including momentum, adaptive scaling, or decoupled weight decay when used. For vanilla minibatch SGD without momentum or weight decay:
The gradient over minibatch \(B_t\) estimates the gradient of the training objective.
The loss defines what is desirable.
The optimizer defines how we move through parameter space.
The dataset defines which regions of that space receive learning signal.
As a qualitative dependency diagram:
3. Data pipeline — the first real control surface¶
3.1 Dataset mixture¶
Consider datasets \(D_i\) with mixture weights \(w_i\):
with:
Mixture weights are a behavioral hyperparameter.
Changing \(w_i\) changes the distribution the model learns from.
3.2 Quantity ≠ diversity ≠ quality¶
More tokens do not automatically mean more useful information.
A conceptual decomposition is:
Excessive duplication reduces novelty and may increase memorization.
3.3 Deduplication¶
Deduplication can happen at different granularities:
- document;
- sequence;
- substring / n-gram;
- semantic embedding;
- perceptual hash for media.
The goal is to reduce:
without destroying semantically legitimate repetition.
3.4 Contamination¶
If an evaluation item \(e\), or a near-equivalent transformation of it, appears in training:
then the benchmark no longer measures pure generalization.
Contamination is both a training-data governance problem and an evaluation-design problem.
See 17_EVALUATION_BENCHMARK_EXPERIMENTATION_DATASHEET.
3.5 Synthetic data¶
Typical pipeline:
The gain depends on:
Risks include:
- teacher-bias amplification;
- error amplification;
- style collapse;
- synthetic monoculture;
- loss of the tail distribution.
4. Tokenization and packing are training parameters too¶
After tokenization:
Training typically uses windows of length \(L\).
Without efficient packing, padding wastes compute:
Sequence packing concatenates examples to drive:
but requires care around:
- attention masks;
- document boundaries;
- position reset;
- cross-example leakage.
5. Pretraining objectives¶
5.1 Causal language modeling¶
This is the classic objective for decoder-only autoregressive models.
5.2 Masked modeling¶
For a set of masked positions \(M\):
See 02_LLM_TRANSFORMER_INFERENCE_DATASHEET.
5.3 Contrastive learning¶
Here \(\tau>0\) is contrastive temperature, not sampling temperature. The denominator includes the positive example as well as the other candidate examples.
See 11_EMBEDDING_RETRIEVAL_RERANKER_DATASHEET.
5.4 Diffusion / flow objectives¶
Diffusion-style:
Training may minimize:
or an equivalent parameterization.
Flow matching:
See 04_IMAGE_GENERATION_DIFFUSION_FLOW_DATASHEET.
6. Optimization mechanics¶
6.1 Effective batch¶
With microbatch \(B_m\), gradient accumulation \(G\), and data-parallel world size \(W\):
In tokens:
It is often more meaningful to compare training runs by tokens per update than by nominal “batch size.”
6.2 Learning rate¶
is one of the most sensitive knobs in the system.
Too low:
Too high can produce:
- divergence;
- catastrophic forgetting;
- reward collapse;
- loss spikes.
6.3 Warmup¶
One linear form is:
Warmup reduces aggressive updates while optimizer statistics and activations are still stabilizing.
6.4 AdamW — mechanical view¶
Moments:
Simplified update:
Fundamental parameters:
- learning rate \(\eta\);
- \(\beta_1\);
- \(\beta_2\);
- \(\epsilon\);
- weight decay \(\lambda\).
6.5 Gradient clipping¶
Global norm, for \(g\neq0\) and threshold \(c>0\):
For \(g=0\), define \(g'=0\). This bounds the gradient norm; the resulting parameter update also depends on the optimizer.
It does not fix a badly specified loss.
7. Training precision¶
Different states may live at different precisions:
Examples:
- FP32;
- BF16;
- FP16;
- FP8 in supported pipelines;
- a frozen 4-bit base in QLoRA.
Mixed precision aims to reduce memory/compute while preserving numerical stability.
8. Full fine-tuning memory model¶
The naive rule:
is not enough.
Training requires approximately:
where:
- \(M_W\): weights;
- \(M_G\): gradients;
- \(M_{opt}\): optimizer state;
- \(M_A\): activations.
With Adam-like optimizers, optimizer states may exceed the size of the weights themselves.
See 09_LOCAL_AI_INFERENCE_RUNTIME_DATASHEET.
9. Gradient checkpointing¶
Without checkpointing, many intermediate activations are retained.
Checkpointing trades memory for recomputation:
This is a training-runtime lever, not a change in the objective function.
10. Distributed training¶
Data parallelism¶
Replicate the model, split the batch.
Tensor parallelism¶
Split operations/tensors within a layer.
Pipeline parallelism¶
Split layers across stages.
FSDP / ZeRO-style sharding¶
Shard:
- parameters;
- gradients;
- optimizer states.
Communication topology becomes a major part of the cost:
11. Supervised Fine-Tuning — SFT¶
Dataset:
Loss:
where \(m\) determines which tokens contribute to the loss.
11.1 Completion-only loss¶
If prompt tokens receive a zero mask:
this avoids training the model to predict the prompt itself when the objective is instruction following.
11.2 Chat template is part of training¶
Messages are serialized into special tokens.
Using message serialization or control-token conventions that are incompatible with training can cause meaningful regression at inference time. Compatibility concerns roles, boundaries, and token semantics; it does not require a complete training example and an inference prefix to be byte-identical.
The chat template is not frontend cosmetics.
12. Instruction tuning versus knowledge injection¶
Small-scale fine-tuning is excellent for:
- format;
- style;
- response policy;
- workflow;
- specific tasks.
It is less reliable as the primary mechanism for factual knowledge injection.
A useful conceptual approximation is:
more than:
For mutable knowledge, retrieval is often the better mechanism.
13. Preference data¶
A pairwise sample is:
where:
- \(y_w\): preferred/chosen;
- \(y_l\): rejected.
The data does not encode only “quality.” It also encodes the preference distribution of the annotator/judge.
See 12_REWARD_VERIFIER_JUDGE_DATASHEET.
14. Reward modeling¶
Reward model:
Bradley–Terry:
Loss:
The reward is a learned proxy objective.
Therefore:
necessarily.
15. Classical RLHF¶
Simplified pipeline:
SFT policy
↓
collect preferences
↓
train reward model
↓
online policy optimization
↓
aligned policy
An abstract objective:
For each prompt \(x\), the KL compares the conditional output distributions. Use \(\beta>0\) and reference-policy support wherever the optimized policy has positive probability; training averages the objective over prompts. The KL term penalizes policy drift.
16. PPO-style post-training¶
PPO uses a clipped policy ratio.
Simplified objective:
Maximize this surrogate, or minimize its negative. Rollouts are sampled from the frozen collection policy \(\pi_{old}\), with advantages treated as fixed during the update. This policy has a different role from the reference policy \(\pi_{ref}\) used for RLHF regularization.
Historically important, although the actor/critic/reward/reference infrastructure makes the pipeline complex.
17. Direct Preference Optimization — DPO¶
DPO removes the explicit reward model from the optimization loop.
A canonical per-pair form, with \(\beta>0\) and positive probabilities for the compared responses in both policies, is:
Fundamental knobs:
- \(\beta\);
- preference dataset;
- reference policy;
- sequence length;
- chosen/rejected quality.
18. KTO / ORPO / offline preference families¶
The important thing is not memorizing acronyms.
Ask instead:
- does it use pairwise preferences?
- does it require a reference model?
- does it directly optimize odds/log-ratios?
- does it combine SFT with a preference penalty?
- is it offline, or does it collect fresh trajectories?
ORPO, for example, integrates a preference penalty directly into SFT and avoids a separate reference model.
KTO works with desirable/undesirable signals inspired by utility asymmetry instead of requiring perfectly paired examples.
The taxonomy will outlive the acronym.
19. Online RL with verifiable reward¶
For tasks with a checker:
or a continuous reward derived from the environment.
Natural examples include:
- mathematics;
- code/tests;
- puzzles;
- tool tasks with verifiable state transitions.
This reduces dependence on a subjective judge, but only for properties covered by the verifier.
20. GRPO — group-relative optimization¶
For a prompt, generate a group:
Rewards:
A conceptual group-normalized advantage is:
The relative advantage reduces the need for an explicit critic.
Important failure surface:
if all rewards are identical and \(\epsilon>0\):
A spread much smaller than \(\epsilon\) also attenuates the normalized signal. A small absolute standard deviation alone does not imply small advantages: when it exceeds the stabilizer, normalization can preserve an order-one relative signal and can also amplify reward noise.
21. DAPO — read it as a system, not a buzzword¶
DAPO emerged as a practical evolution of large-scale RL, combining decisions around clipping, sampling, and token-level treatment to improve stability and efficiency in reasoning training.
The generalizable lesson is:
It depends on:
- sampling distribution;
- dynamic filtering;
- reward design;
- clipping;
- rollout length;
- infrastructure.
22. GSPO — sequence-level ratio¶
GSPO replaces a token-level ratio with a sequence-normalized ratio:
or:
This is especially relevant to MoE RL, where token-level routing differences can make importance ratios fragile.
2026 snapshot: GSPO remains an important example of how the statistical unit of the update can matter as much as the reward function.
23. On-policy versus off-policy¶
On-policy¶
Data comes from the current policy:
Pros:
- signal aligned with current behavior.
Cons:
- expensive;
- requires rollout infrastructure;
- unstable.
Off-policy / offline¶
These describe different axes. Off-policy learning updates a target policy using data from a different behavior policy; it can still collect fresh experience online, for example with replay.
Offline learning uses a fixed, pre-collected dataset without new interaction:
Potential advantages of a fixed dataset:
- reuse of collected experience;
- lower cost of additional data collection;
- controlled, reproducible data comparisons.
Risks:
- distribution mismatch;
- extrapolation error and unstable optimization.
Off-policy or offline learning is not inherently cheap or stable; total cost also includes data acquisition and optimization.
24. Reward hacking and overoptimization¶
If the reward model is a proxy:
then stronger optimization can eventually produce:
This is a case of Goodhart's law.
See 12_REWARD_VERIFIER_JUDGE_DATASHEET.
25. PEFT — the mathematical idea¶
Full fine-tuning:
with unrestricted \(\Delta W\).
PEFT constrains the update to a smaller parameterized subspace.
26. LoRA¶
For:
LoRA uses:
with:
where:
Update:
or a variant scaling rule, depending on the implementation.
27. LoRA trainable parameter count¶
Approximately:
per target matrix.
Therefore:
when \(r\) is small.
28. LoRA knobs¶
| Parameter | Tag | Controls |
|---|---|---|
r |
TRAIN |
capacity of the update subspace |
alpha |
TRAIN |
update scaling |
| target modules | TRAIN |
which matrices receive adapters |
| dropout | TRAIN |
regularization |
| initialization | TRAIN |
initial condition of the adaptation |
| bias training | TRAIN |
whether biases are updated as well |
There is no universally optimal rank.
29. Target modules¶
In a Transformer these may include:
- Q;
- K;
- V;
- O;
- gate/up/down projections;
- embeddings/output in specific cases.
More modules:
but also:
30. QLoRA¶
The idea:
base weights: quantized + frozen
↓
forward/dequant compute
↓
train LoRA adapters
The base is excluded from parameter updates:
The adapters \(A,B\) are optimized. Freezing the base does not assert that the loss has a zero mathematical derivative with respect to its weights; base-weight gradients are not accumulated for optimization. Adapter gradients can also be zero at particular steps: with the standard initialization \(B=0\), the initial loss gradient with respect to \(A\) is zero.
QLoRA dramatically reduces the memory footprint of the frozen base, but training still requires:
- activations;
- adapter gradients;
- optimizer state for the adapters;
- temporary dequantization buffers.
Therefore:
31. DoRA¶
DoRA separates weight magnitude from direction.
Using the linear-layer convention \(W,V\in\mathbb R^{d_{out}\times d_{in}}\) and a magnitude vector \(m\in\mathbb R^{d_{out}}\), the decomposition for nonzero rows of \(V\) is:
Each output row is normalized over its input dimension; the corresponding magnitude is broadcast across that row. A transposed weight convention expresses the same operation column-wise. The direction receives a low-rank adaptation; magnitude is learned separately. Zero row norms require an explicit numerical convention in the implementation.
Goal: approach more of the flexibility of full fine-tuning while retaining PEFT.
Trade-off:
- greater flexibility;
- more overhead than plain LoRA.
32. LoRA initialization is now a real axis¶
Modern implementations support strategies such as:
- default no-op;
- Gaussian;
- PiSSA;
- EVA;
- LoftQ-oriented initialization;
- CorDA-like variants.
The choice can affect:
So “LoRA” alone does not fully specify the adaptation dynamics.
33. Adapter composition¶
Adapters can be:
- loaded separately;
- weighted;
- combined;
- merged into the weights.
A linear combination:
can produce interference.
Do not assume perfect compositionality.
34. Model merging — parameter space¶
Given checkpoints \(\theta_i\):
Linear merge¶
with weights typically normalized.
35. Task vectors¶
Given base \(\theta_0\):
Merge:
This view treats fine-tuning as a displacement vector in parameter space.
36. TIES / DARE¶
TIES seeks to reduce interference through:
- sparsification;
- sign consensus;
- merging only compatible deltas.
DARE applies random dropping plus rescaling to deltas before merging.
The general idea is that:
can make a simple average destructive.
37. SLERP and merge geometry¶
SLERP interpolates along spherical geometry between vectors.
For two unit vectors separated by angle \(\omega\):
Here \(t\in[0,1]\) and \(0<\omega<\pi\). Coincident endpoints use the continuous limit; antipodal endpoints do not determine a unique interpolation arc. Implementations need explicit handling when \(\sin\omega\) is zero or numerically close to zero.
Useful when linear interpolation does not preserve magnitude/direction well.
38. Merge compatibility¶
Before merging models, verify:
- architecture;
- tensor shapes;
- tokenizer;
- vocabulary size/order;
- RoPE/position configuration;
- normalization;
- base lineage.
39. Knowledge distillation¶
Teacher:
Student:
A typical loss:
Here \(T>0\) is distillation temperature, again distinct from sampling temperature, and \(\lambda\in[0,1]\). The teacher is fixed and both distributions use the same category support; for token-level distillation this requires compatible vocabularies or an explicit alignment. Sequence-level distillation can be used when directly aligned logits are unavailable.
40. Sequence-level distillation¶
For generative models, the teacher often produces trajectories:
which become training data for the student:
This is behavior distillation even when the teacher's logits are unavailable.
41. Reasoning distillation¶
The teacher generates:
The student learns from traces or filtered answers.
Risk:
This is why verifier/filtering quality is central.
42. On-policy distillation¶
The student generates its own trajectory; the teacher supplies a distribution or feedback over states visited by the student.
Advantage:
it reduces mismatch between:
and:
This is a strong trend in modern post-training toolkits.
43. Dataset distillation¶
Instead of compressing only the model, dataset distillation tries to construct a compact dataset:
such that training on it approximates training on:
This is a separate axis from knowledge distillation.
44. Pruning¶
Mask:
with:
Unstructured¶
Individual weights are removed.
Structured¶
Remove structures such as:
- heads;
- neurons;
- channels;
- layers;
- experts.
Structured pruning tends to map better onto conventional hardware.
45. Sparsity does not imply speedup¶
if the kernels/hardware cannot exploit the sparsity pattern.
Always distinguish:
from:
and:
46. Continual learning¶
A new distribution \(D_{new}\) may improve the new task while degrading old ones.
Catastrophic forgetting:
Countermeasures include:
- replay;
- regularization;
- separate adapters;
- data mixtures;
- lower learning rate;
- selective freezing.
47. Curriculum¶
The data distribution changes over training time:
instead of remaining constant.
A curriculum may be organized by:
- difficulty;
- length;
- domain;
- reward;
- confidence;
- stage.
The order of exposure becomes part of the algorithm.
48. Long-context training¶
Increasing sequence length affects:
- the position system;
- activations;
- attention cost;
- optimizer throughput;
- packing;
- loss normalization.
Training at 1M tokens is not simply changing max_seq_len.
Contemporary tooling explicitly treats loss, positions, activation memory, and per-sequence GPU memory as separate bottlenecks.
49. Multimodal adaptation¶
For a VLM:
vision encoder
↓
projector / connector
↓
LLM
We may:
- freeze the vision encoder;
- train only the projector;
- train the LLM + projector;
- fine-tune the entire system.
Each choice changes:
and the risk of destroying pretrained representations.
See 10_MULTIMODAL_VLM_OMNI_DATASHEET.
50. Diffusion/flow adaptation¶
LoRA is also common in:
- attention projections;
- text encoders;
- DiT blocks.
The same low-rank concept remains, but the objective function and observables differ from LLM SFT.
See 04_IMAGE_GENERATION_DIFFUSION_FLOW_DATASHEET.
51. Data-quality feedback loop¶
A mature system looks like:
train
↓
evaluate
↓
find failure clusters
↓
collect / generate targeted data
↓
filter / verify
↓
retrain
This is active data engineering.
The benchmark begins to guide data acquisition.
Risk: overfitting to the benchmark.
52. Training observables¶
Never monitor loss alone.
Optimization¶
- train loss;
- eval loss;
- gradient norm;
- parameter norm;
- learning rate;
- clipping fraction.
Throughput¶
- tokens/s;
- samples/s;
- step time;
- MFU/compute utilization when available.
Memory¶
- allocated;
- reserved;
- peak;
- activation/offload.
RL¶
- reward mean/std;
- KL;
- entropy;
- response length;
- zero-variance groups;
- clipped fraction;
- success rate.
53. Loss curve ≠ capability curve¶
does not guarantee:
especially under:
- overfitting;
- a misaligned objective;
- contaminated evaluation;
- preference overoptimization.
Evaluation must measure the desired behavior directly.
54. Training parameter coupling matrix¶
| ↑ variable | Primary effect | Common secondary effect |
|---|---|---|
| batch/tokens per update | less noisy gradient | may require a different LR |
| LR | update magnitude ↑ | instability/forgetting ↑ |
| context length | information per sample ↑ | memory/compute ↑ sharply |
| LoRA rank | adaptation capacity ↑ | trainable memory ↑ |
| LoRA targets | degrees of freedom ↑ | interference/overfit ↑ |
| preference beta | changes constraint/strength | style/capability trade-off |
| RL group size | improves reward-relative estimate | rollout cost ↑ |
| rollout length | exploration/horizon ↑ | cost/variance ↑ |
| KL penalty | policy drift ↓ | exploration/capability gain may ↓ |
| distillation temperature | changes soft-target smoothness | changes dark-knowledge transfer |
These relationships are not universally monotonic.
55. Failure surfaces¶
Optimization divergence¶
- NaN;
- loss explosion;
- gradient explosion.
Catastrophic forgetting¶
New-task performance rises while old-task performance falls.
Mode/style collapse¶
Responses converge toward a narrow template.
Reward collapse¶
Reward rises while real quality falls.
Data contamination¶
Evaluation stops being a valid diagnostic.
Synthetic monoculture¶
Diversity decreases.
Overfitting¶
Merge interference¶
Individual capabilities cancel one another out.
56. Local hardware reality¶
On a local workstation, distinguish:
Inference feasible¶
from:
Full training feasible¶
A GPU that can run a 12B model in Q4 cannot necessarily train that same 12B model.
Assess feasibility separately in peak VRAM, wall-clock time, and runtime support:
- for the same base model, adapter targets, batch, and sequence length, QLoRA usually reduces base-weight memory relative to LoRA with a BF16/FP16 base;
- quantization metadata, dequantization buffers, activations, and kernel support still affect total VRAM and time; lower base-weight memory does not guarantee a faster run;
- prompt tuning and small adapters reduce trainable state but still require the base and the activations needed to train those parameters;
- full fine-tuning adds gradient and optimizer state for the updated base parameters, while pretraining also depends strongly on the data volume and compute budget.
There is no universal ordering of these methods across all hardware, models, and sequence lengths.
Calculate first:
57. Experimental protocol — fine-tuning¶
When comparing two configurations, hold constant:
- base checkpoint;
- tokenizer/template;
- dataset split;
- seed set;
- number of tokens;
- evaluation harness.
Change only the hypothesis under test.
Example:
H0: r=16 and r=64 do not meaningfully change domain quality.
control:
base model
dataset
target modules
LR
steps
seed set
variable:
LoRA rank
observe:
validation loss
target benchmark
forgetting benchmark
peak VRAM
training time
See 17_EVALUATION_BENCHMARK_EXPERIMENTATION_DATASHEET.
58. Provenance tags specific to this document¶
In addition to the global tags:
| Tag | Meaning |
|---|---|
DATA |
data composition/transformation |
TRAIN |
training hyperparameter |
ALIGN |
preference/reward/alignment stage |
PEFT |
parameter-efficient adaptation |
DISTILL |
knowledge/dataset distillation |
MERGE |
parameter/model merging |
See CONVENTIONS.
59. SOTA snapshot — 2026¶
The relevant picture in October 2026 is less “which algorithm won?” and more a convergence of practices:
- SFT remains foundational, but modern post-training separates offline preference methods, online RL, and reward/verifier training.
- Mature tooling exposes SFT, DPO, GRPO, KTO, RLOO, reward modeling, and distillation as distinct families.
- RL for reasoning has made rollout infrastructure, sampling, and sequence-level statistics as important as the nominal loss.
- GSPO popularized sequence-level policy ratios as a more stable alternative in some regimes, particularly MoE RL.
- PEFT is no longer synonymous with vanilla LoRA: DoRA, initialization strategies, adapter mixing, and quantized training form a space of their own.
- Model merging has become practical engineering, with linear merge, SLERP, task arithmetic, TIES, DARE, and variants.
- Modern distillation includes logits, sequences, reasoning trajectories, and on-policy teacher/student loops.
- Synthetic data requires curation and verification; “generate more examples” is not a sufficient data policy.
60. Checklist for dissecting any checkpoint¶
- What is the base model?
- What tokenizer/template?
- How many pretraining tokens?
- What data mixture?
- What objective?
- Was there continued pretraining?
- Was there SFT?
- Was the loss prompt+completion or completion-only?
- Was preference training used?
- DPO/KTO/ORPO/RL/GRPO/GSPO or equivalent?
- What reward/verifier?
- Online or offline?
- Was synthetic data used?
- Was there distillation?
- Is it a merge?
- What is the base lineage of the merged models?
- Was there pruning?
- Was PEFT used?
- LoRA rank/alpha/targets?
- QLoRA/DoRA?
- What training sequence length?
- What optimizer/LR schedule?
- Which benchmark guided selection?
- Is there contamination risk?
- Which checkpoint is actually served at inference time?
61. Mechanical summary¶
This is a qualitative dependency diagram. The composition symbol summarizes interacting influences; it does not define a quantitative law or a literal composition of specified mathematical functions.
Architecture defines the space of what is possible.
Data and objectives determine where the system is pushed.
Optimization determines the trajectory through parameter space.
Post-training determines which regions of behavior are reinforced or suppressed.
Inference simply operates the resulting system.
Snapshot references¶
- Direct Preference Optimization — https://arxiv.org/abs/2305.18290
- ORPO — https://arxiv.org/abs/2403.07691
- QLoRA — https://arxiv.org/abs/2305.14314
- DoRA — https://arxiv.org/abs/2402.09353
- DAPO repository/paper — https://github.com/BytedTsinghua-SIA/DAPO
- GSPO — https://arxiv.org/abs/2507.18071
- Hugging Face TRL docs — https://huggingface.co/docs/trl/index
- Hugging Face PEFT docs — https://huggingface.co/docs/peft/main/index
- Hugging Face PEFT LoRA — https://huggingface.co/docs/peft/main/package_reference/lora
- mergekit merge methods — https://github.com/arcee-ai/mergekit/blob/main/docs/merge_methods.md
- TIES-Merging — https://arxiv.org/abs/2306.01708
- DARE / Language Models are Super Mario — https://arxiv.org/abs/2311.03099
- Synthetic data generation/curation survey — https://arxiv.org/abs/2406.15126
- Knowledge & Dataset Distillation survey — https://arxiv.org/abs/2504.14772