05

Which policy made this?

Good answers can be old behavior. The response text cannot tell you its provenance.

The answer did not change its author

Suppose model version 12 generated a rollout. The trainable model has since advanced to version 14. The response still says 5, and its reward is still 1. Has it become version-14 data?

No. A useful answer can be old behavior. The text cannot tell you the policy that generated it.

Three names, three jobs

The behavior policy is the distribution that generated the recorded actions. For this example, πbeh=πv12\pi_{\mathrm{beh}}=\pi_{v12}.

The current policy is the trainable policy under consideration now. Here, πcur=πv14\pi_{\mathrm{cur}}=\pi_{v14}. In ratio-based methods such as PPO and GRPO, comparisons use the current policy's probabilities and those of the behavior or old policy that generated the actions. PPO §3 · DeepSeekMath §4.1.1

An optional reference policy supplies a different comparison—for example, a KL penalty that discourages moving too far from a reference distribution. It is not automatically the behavior policy; it is not the reward model or the group mean either. Our notation could name it πref−v1\pi_{\mathrm{ref-v1}}, separately identified from both versions above. InstructGPT §3.5 · DeepSeekMath equation 3

These are functional roles, not necessarily three unrelated architectures or three permanent model copies. At fresh collection, current and behavior weights may coincide. A method may omit a reference role altogether.

Figure 005The data keeps its origin
Separate behavior, current and optional reference policy lanesBehavior v12 generated stored data. Current policy changes from v12 to v14. The data retains v12 provenance. Reference ref-v1 is a separate optional comparison, not the generating policy or reward baseline.BEHAVIOR · GENERATED THE DATACURRENT · UPDATE TARGETREFERENCE · OPTIONAL ANCHORv12stored rollout: v12v12v14updateref-v1behavior comparisonoptional reference comparisonSeparate behavior, current and optional reference policy lanesBehavior v12 generated stored data. Current policy changes from v12 to v14. The data retains v12 provenance. Reference ref-v1 is a separate optional comparison, not the generating policy or reward baseline.BEHAVIOR · GENERATED THE DATACURRENT · UPDATE TARGETREFERENCE · OPTIONAL ANCHORv12stored rollout: v12v12v14updateref-v1behavior comparisonoptional reference comparison
Changing current weights does not rewrite the origin of stored actions. Version labels identify snapshots, not a numerical distance or a safe age. The optional reference is not the verifier or group mean.

On-policy is about provenance

An introductory on-policy distinction asks whether the data comes from the policy used for the update, rather than an older or different behavior policy. It is not a label for whether an answer is correct. Spinning Up: kinds of RL algorithms

There is a practical qualification: original PPO can reuse a freshly collected batch for several minibatch epochs. “On-policy” therefore does not mean collecting a new rollout before every individual gradient step. It also does not grant unlimited reuse of old data. PPO abstract and Algorithm 1

Check your understanding

May the trainer use the version-12 rollout to update version 14?

Reveal answer

We cannot decide from the response or policy labels alone. We know who generated the data, but need the chosen algorithm's acceptance and correction rules. There is no universal safe age or version gap asserted here.

We can finally put collection, feedback, and learning on one timeline.