- Rating
- 3
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper introduces DHKR, a framework for adapting frozen language models by controlling the availability of external representation-intervention paths. A two-level Knowledge Steering Layer combines input-dependent routing with a rule-based controller that monitors training and routing statistics. The framework distinguishes learning intervention parameters, allocating inputs across paths, and deciding which paths participate in optimization. Experiments compare Controller, Static, Scheduled, and Full configurations under a shared regularized objective. The Controller achieves lower validation loss across three seeds, while counterfactual probes examine the contribution of learned allocation. Separate expanding trajectories document routing redistribution and optimization after path release. Additional experiments assess generation quality, calibration, and computational cost.
Critical strengths
- The paper distinguishes parameter learning, input-conditioned allocation, and structural availability, then examines them through useful controls.
- Counterfactual routing probes support the contribution of learned allocation. The three-seed comparison also shows consistent validation-loss improvements over static and full-from-start configurations.
Critical weaknesses
- The main comparison leaves feedback-dependent timing entangled with execution details. Controller and Scheduled both expand at step 5 and retain the same capacity afterward. Their difference therefore requires an explanation beyond the release schedule.
- The strongest Controller result concerns loss and token accuracy. In the separate generation experiment, fixed capacity performs better on all six metrics. Generation results for the main Controller would clarify its practical benefit.
- Key implementation details remain implicit, including the complete release rule, thresholds, regularizer definitions, and coefficients. These details matter because transition handling appears central to the gain.
Questions for authors
- What exact execution differences separate Controller from Scheduled, and what happens when their transition operations are matched?
- How does the main Controller compare on generation quality and cumulative training compute across the three seeds?