- Rating
- 3
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper addresses visual rule induction and execution in large vision-language models. It proposes Latent Rule Reasoning (LRR), which sequentially generates continuous rule representations and target-state representations before producing an answer. Latent Rule Self-Distillation (LRSD) trains this framework using complete visual observations to guide reasoning from incomplete inputs, together with rule reconstruction, target-feature alignment, and answer supervision. Experiments on abstract visual reasoning and general visual understanding benchmarks demonstrate performance improvements and provide evidence of transfer beyond the fine-tuning benchmarks.
Critical strengths
- The framework is well motivated and closely aligned with the problem structure. Separating rule induction from rule execution provides a clear organization for latent reasoning, while distinct supervision objectives encourage the intermediate representations to capture relations and their visual consequences. This constitutes a meaningful framework-level contribution.
- The training approach coherently combines semantic grounding with cross-view self-distillation. Sections 3.3–3.4 connect rule representations to explicit rule descriptions and target representations to fixed visual features, then introduce consistency learning to incorporate examples without explicit rule annotations. This provides a practical approach to learning from different levels of supervision.
- The empirical evaluation is comprehensive, covering in-distribution abstract reasoning, cross-benchmark transfer, and general visual understanding. Tables 1–3 show consistent improvements over the backbone and competitive results against the evaluated methods, with a particularly notable advantage on SpatialEval. The component, latent-length, and model-scale analyses in Tables 4–6 further strengthen the empirical case and help establish the contributions and limitations of the design.
Critical weaknesses
- The connection between the intended roles of the latent representations and their learned behavior could be clearer. Although rule reconstruction and target alignment provide meaningful supervision, Figure 4 primarily presents rule descriptions and final predictions without establishing how these descriptions relate to the student’s inference-time representations. Individual latent tokens need not have directly interpretable meanings, but clarifying the provenance of the displayed rules and any existing evidence of the two stages’ functional specialization would strengthen the mechanistic interpretation. This is an explanatory limitation rather than a fundamental flaw.
- Some hyperparameters and implementation details are not fully documented in Section 4 and Appendix B. Additional information about the training-data mixture, rule-annotation coverage, loss weights, and the rule decoder and token pruner would make the method easier to reproduce. These appear to be straightforward documentation issues that could be addressed with a compact implementation summary.
- A few reporting details require clarification. The benchmark named VASR in the text appears as VAP in Table 2, without an explanation of their relationship. The tables also do not indicate whether results come from single or multiple runs. This matters particularly for small margins, such as the 0.11-point advantage over the strongest comparator on MMBench. Consistent naming and a clear statement of the reporting protocol would improve precision without changing the broader positive findings.
Questions for authors
- What is the source of the rule descriptions in Figure 4: dataset annotations, manual explanations, or outputs from the rule decoder? If they are model-generated, do they use complete-view teacher representations or student representations generated under inference conditions?
- Could the authors provide a brief implementation summary covering the training-data mixture, rule-annotation coverage, loss weights, and the configurations of the rule decoder and token pruner?
- Does VAP in Table 2 refer to VASR? Please also clarify whether Tables 2–3 report single-run results or averages over multiple runs, and summarize any already available variability estimates.