Shiyuan Feng, Huan-ang Gao, Haohan Chi, Hanlin Wu, Zhilong Zhang, Zheng Jiang, Bingxiang He, Wei-Ying Ma, Ya-Qin Zhang, Hao Zhou
4 min
Abstract
Reinforcement learning with verifiable rewards (RLVR) is a powerful recipe for improving language-model reasoning, but it is expensive to repeat on every new strong model because the target model must generate many rollouts during training. As models scale, post-training itself becomes a bottleneck. We study a weak-to-strong alternative: run RL on a smaller model where rollouts are cheaper, then reuse what that RL run learned to improve a stronger target model. Directly distilling the post-RL weak teacher is not enough, because the teacher's final policy mixes useful RL gains with the limitations of the smaller model. We propose Direct On-Policy Distillation (Direct-OPD), which transfers the teacher's RL-induced policy shift instead. Direct-OPD compares the post-RL teacher with its own pre-RL reference and treats their log-ratio as a dense implicit reward for the student. In plain terms, the checkpoint pair tells us which actions RL made the weak model more or less likely to take, and Direct-OPD applies that signal on the stronger student's own on-policy states. This directly reuses the weak model's RL supervision signal without running sparse-reward RL on the target model. Empirically, Direct-OPD consistently leverages weaker teachers to improve stronger target models; notably, it boosts Qwen3-1.7B from 48.3% to 58.3% on AIME 2024 in just 4 hours on 8 A100 GPUs. It outperforms step-matched direct RL and enables the sequential composition of multiple policy shifts. Our results show that RL outcomes can be reused across model scales as implicit reward signals, not merely as final models to imitate.
Sam: The results are notable. In one test, they improved a model's performance on a competitive mathematics benchmark in roughly four hours—achieving results that typically require far more computing time and resources using standard methods.
Alex: How do they stop the large model from just going off the rails when it receives this signal? If you're pushing it in a new direction, couldn't it overcorrect?
Sam: That's a real risk, and the authors address it directly. They use something called KL-regularization—think of it as a safety tether. It's a mathematical constraint that limits how far the model's behavior can shift in any one step. Like a guardrail on a steep road: it doesn't stop you from moving forward, but it prevents you from veering off the edge. They also use an adaptive controller that adjusts the strength of that guardrail based on how strong the incoming signal is, so the learning stays steady rather than lurching around.
Alex: So the system is actively managing the balance between absorbing new knowledge and not losing what the model already knows.
Sam: That's a good way to put it. And there's one more technical piece worth mentioning. To make the signal itself more reliable, the authors use a technique called Rao-Blackwellization. In practice, this means they focus the signal on the most probable next words the model might generate—filtering out random noise so the "reasoning compass" points somewhere consistent rather than flickering.
Alex: So you're not just transferring knowledge—you're transferring a cleaned-up, stable version of it.
Sam: Right. And taken together, these pieces—the policy shift, the safety tether, the noise reduction—add up to a system where the cost of discovering how to reason is separated from the cost of scaling that reasoning to a larger model. A small model does the exploration. Once it finds a better path, the map gets handed to the larger model.
Alex: That's a genuinely different way of thinking about the problem. Instead of asking "how do we train a large model to reason," the question becomes "how do we efficiently move reasoning ability from one place to another."
Sam: And the paper suggests that reasoning, treated this way, behaves more like a transferable skill than something that has to be rebuilt from scratch at every scale. Whether that holds across a wider range of tasks and model architectures is something further research will need to establish—but as a proof of concept, it makes a clear and well-supported case.
Alex: A thought-provoking result. Thanks for walking us through it.
Sam: Thanks for having me.
Alex: And thanks to everyone listening. This has been ResearchPod.