W1. The independent contribution of modularization remains insufficiently established given the routing-instruction control.
In Table 2, providing the same Foresight router’s decisions as instructions to monolithic LoRA achieves 16.8%, compared with 15.8% for TurnRoute. The reported parameter counts correspond to approximately 323.0M trainable parameters for the former and 807.5M for the latter. The authors correctly acknowledge that the routing signal explains much of the performance gain. My concern is therefore not that this important control is missing, but that its result places greater importance on establishing what expert modularization contributes beyond being executable.
Preserving comparable performance in exchange for useful modular properties can certainly constitute a contribution; achieving the highest resolution rate is not necessary. However, the experiments do not directly demonstrate that updating or replacing one specialist preserves the effectiveness of the remaining capabilities and the composed system. Section 3.1 establishes that adapters can be retrained or replaced independently at the parameter level, but parameter independence does not itself establish behavioral compatibility after replacement. Meanwhile, Appendix E reports that training the four adapters costs nearly four monolithic training runs and that the 14B system requires approximately 1.6 times the resident memory of monolithic LoRA.
I am not asking the authors to validate every potential use of modularity. Nevertheless, some direct evidence is needed to establish what these additional costs buy that the routing-instruction control does not already explain. Reporting patch production for that control would help determine whether the paper’s clearest behavioral improvement also primarily comes from routing. A focused specialist-update or replacement experiment would instead test a practical benefit of modularity. This is a central concern for my recommendation.
W2. The evidence more directly establishes behavioral differentiation than semantically well-defined capability decoupling.
Table 1 provides useful initial evidence, but differences between specialists do not necessarily show that the corresponding capabilities have been effectively isolated into their designated modules. For example, on the verification probe, the verification specialist and monolithic LoRA both achieve 6.2%, the base model achieves 6.0%, and the off-capability adapter achieves 3.5%. This is also consistent with some adapters preserving a base-model capability while others degrade it; the between-adapter gap alone does not distinguish these explanations.
The random-supervision-token control is valuable: it shows that the code specialist’s lower end-to-end performance cannot simply be attributed to receiving fewer supervised tokens. However, this control is evaluated only through end-to-end resolution, not through the capability probes. It therefore does not directly establish whether capability-based masking produces more clearly defined specialization than a non-semantic partition with a comparable supervision budget.
Furthermore, Figure 4 analyzes the actual behavior of monolithic and capability-agnostic LoRA, rather than TurnRoute, while Figures 5–6 report adapter selections and switching patterns. Selecting an adapter named “verification” does not automatically establish that the resulting turn performs verification. An analysis of routing-label versus actual-action correspondence in existing TurnRoute trajectories, together with probe results for the existing random-supervision control, would more directly support the central interpretation that these modules perform their intended roles.