- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
ROAST builds a task specific steering vector by using model generated rollouts split by an outcome verifier. It compares the final token activations between correct and incorrect generations for each question. Then takes the mean direction of each question and renormalizes them. The resulting vector is then added to the intermediate MLP layer activation while decoding. There were many models and tasks tested however not all combinations. By using matched answers they show benefit from keeping generation context and outperform no steer by 9.66% on GSM8K/Qwen3-0.6B.
Critical strengths
- Ablating with matched corpus is good. Table 5 keeps rollouts, labels, final answers and number of pairs. Removing only trajectories from the prompt. Restoring the trajectory improves all six matched columns, including +6.05 points on GSM8K/0.6B. It's better to have these types of ablations compared to an unmatched metric vs an answer.
- Its fairly simple method to deploy and test on multiple models. No parameters changed and can be used without any added context. The disclosure of negative results, strength sensitivity, and evaluation limitations helps delimit the findings.
Critical weaknesses
The contribution is insufficiently distinguished from closely related prior work. ALS [1] already constructs mean-difference steering vectors from automatically verified successful and unsuccessful model generations, with final-token extraction explicitly described in Section 2 of its original version. AdaRAS [2] self-samples multiple trajectories for the same input, pairs opposite correctness outcomes, and uses activation mean differences to steer MLP activations (Sections 3.1–3.4). Neither work is discussed or empirically compared against. ROAST differs in its aggregation, normalization, and intervention details, and its matched source-context ablations are useful. However, without comparisons to these predecessors, it remains unclear whether these differences establish a sufficiently substantial contribution beyond the existing trajectory-based steering recipe.
References
[1] Nathan Egbuna, etal. Amortized Latent Steering: Low-Cost Alternative to Test-Time Optimization. 2025. arXiv:2509.18116v1. https://arxiv.org/abs/2509.18116v1
[2] Fangan Dong, etal. Identifying and Transferring Reasoning-Critical Neurons: Improving LLM Inference Reliability via Activation Steering. 2026. arXiv:2601.19847v1. https://arxiv.org/abs/2601.19847v1
The context controls do not fully establish what the steering direction captures. Table 6 tests one model and task at a single strength, α=3. It shows that intact trajectory context produces a better direction under this setting. However, corrupted contexts may produce harmful directions, and different directions may require different strengths. The results therefore do not establish that the vector captures a reusable correct-reasoning mechanism. A strength sweep and readouts that exclude the final answer would help clarify this.
The theory does not yet explain the practical benefit of grouping. Assumption A2 directly assumes that within-question averaging does not reduce variance as the pair count grows. Sharing rollouts across pairs does not, by itself, establish this assumption. The proof also compares an unnormalized naive estimator with a normalized grouped estimator. Appendix A.4 acknowledges both limitations, but without a comparison between equally normalized estimators, the theoretical advantage attributable to grouping remains unclear.
The noise results are too limited to establish broad robustness. Table 7 uses one seed on two tasks. Grouping performs better than nongrouped aggregation, but retaining an improvement over no intervention is task-dependent: at 20% label flips, grouped ROAST remains above baseline on GSM8K but falls to 46.02 on TruthfulQA, below the 48.78 baseline. The experiment also tests independent symmetric flips, rather than systematic verifier errors. It supports a benefit of grouping in these tests, but not a general robustness claim.
Questions for authors
-
What are the main advances over ALS [1] and AdaRAS [2]? Can controlled comparisons using the same rollout pool, evaluation protocol, and comparable tuning budgets demonstrate the value of those advances?
-
Section 4.4 intervenes at the MLP post-activation output, while §1/§2/App. E describe the method as operating on the residual stream and Related Work excludes 'localized-component' methods from ROAST's family. Which characterization holds, and do baseline vectors (extracted at the residual stream) use the same injection component?
-
Does the ordering of the extraction contexts in Table 6 hold across steering strengths and on another reasoning model or task? Do the gains persist when steering vectors are extracted from activations just before the final answer begins, to test their dependence on terminal-answer features?
-
What supports A2 under the actual rollout-sampling process? For a fixed question, how does the variance of its mean-difference estimate change across repeated rollout draws as the number of independently sampled rollouts increases? Can the theoretical comparison use Norm(v_naive) and the grouped estimator, with the roles of question count and rollout count stated explicitly?