- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper studies teacher assignment in multi-teacher on-policy distillation. The standard recipe sends each student rollout to one domain teacher; Capability-OPD instead builds an offline vocabulary-id table and distills each generated token against the specialist with the larger gold-token log-probability lift over a shared initialization. Teachers grow from the same π0; routing does not look at context. The main runs concatenate a math segment and a code segment in one sample. On Qwen2.5-7B, Table 10 reports PER-TOKEN vs MATH-ONLY +1.67 on the three code sets and +0.43 n.s. on the three math sets; vs CODE-ONLY +1.49 on math and −1.01 on code. The code gap vs MATH-ONLY flips to −1.42 on single-domain data. The same comparison is not detected on Qwen3-4B or a 30B-A3B MoE. The seven-benchmark mean is not significant. Training pays one extra frozen-teacher forward per rollout relative to per-sample routing.
Critical strengths
1.The paper isolates “who to hear at each step” as a granularity variable. Multi-teacher OPD really does have to choose a teacher at each prefix. The authors freeze the teacher pair, data, optimizer, and step count, keep reverse KL, and only replace the sample-level teacher with a vocabulary-id lookup. This is consequential because granularity can be asked about without also changing the teachers or the loss.
2.Finer assignment yields a checkable multi-domain compromise, not a concatenation of two specialists’ best scores. A sample-level teacher hurts the other domain; a finer assignment recovers some of that drop, but still trails the matching specialist on that specialist’s own domain. The code-source swap, multiple seeds, and the mixing-fraction sweep keep the same direction. This is consequential because, for a unified student, the right comparison is the multi-domain compromise rather than stitching together two experts’ peak scores. That comparison still does not identify the table as capability detection.
Critical weaknesses
1.The problem setting and usable range are narrower than the introduction; concatenation shows a controlled domain switch, not natural multi-capability reasoning. Figure 1 shows a domain-B token inside one solution; §3.1 stitches a math item to a code item. Concatenation can be a valid controlled experiment. It shows that a sample-level tag cannot choose a possibly better teacher for each segment. Shared initialization and a same-family student define the present operating range. The seven-benchmark mean vs MATH-ONLY is +0.68 with a CI through 0; every rollout also requires a forward pass from both frozen teachers. This is consequential because the headline 7B result is then a limited empirical edge under constructed switches and extra teacher compute, not evidence that the method identifies capabilities during natural generation. Table 3’s 7B / 4B / MoE comparison also changes model generation and experimental setup together.
2.Routing is a context-independent vocabulary lookup; the present experiments do not show that this lookup identifies the capability a token needs, and they do not rule out simpler assignment. The student writes a vocabulary id and looks up a preassigned teacher, without reading the current prefix. Token identity can serve as a proxy for capability ownership; that proxy does not use context. RANDOM-LABEL is reported only on the seven-benchmark mean (−0.39 n.s.). Figure 4’s spans 1–32 are a plateau; majority-vote budget shifts are associated with the drop; Figure 5’s mass is scaffolding tokens. Recomputation after a teacher-pair or family change is expected for an offline table unless the manuscript claims transfer. Frequent switches do not by themselves make adjacent supervision contradictory. This is consequential because the experiment that would identify the table — matching teacher share and switching frequency, then comparing the static lookup with random token or span assignment on the math and code pools — is not in the present tables.
Questions for authors
1.On mixed reasoning that is not two items concatenated (natural-language reasoning inside contest code, symbolic spans inside a derivation), are Table 10’s pairwise gaps still there: PER-TOKEN vs MATH-ONLY on the three code sets, and PER-TOKEN vs CODE-ONLY on the three math sets? If not, can the headline be stated as a condition on concatenated mixtures, shared-root teachers, and a same-family student?
2.After matching the identity table’s teacher share and switching frequency, does the static vocabulary lookup still beat random token assignment or span assignment? Please report this on the three math sets and the three code sets, not only on the seven-benchmark mean. Is the training table at τ=0 still dominated by function words?
3.Relative to PER-SAMPLE, what is the end-to-end training cost of the extra frozen-teacher forward (wall-clock / teacher FLOPs)? Can the claimed capacity pattern be reproduced inside one model family with the other training and evaluation conditions aligned, rather than Qwen2.5-7B vs Qwen3-4B vs 30B-A3B?