-
ATWD does not act on the problem that motivates it, and the title misdescribes the method. The abstract and introduction motivate the work with FPRM's max-residual halting rule: "one lagging token forces every other, already-converged token to keep iterating at full cost – the gap this paper addresses" (L. 075–077; also L. 013–015). ATWD leaves this rule unchanged. Halting is still the sequence-level maximum of Eq. 2, which the evaluation path further reduces across the batch (L. 154–156, 352). The shared block still evaluates every token at every iteration (L. 429–432). A token whose residual is below τ never has its step-size decayed (L. 174–177), so converged tokens keep iterating at their current step-size. The paper acknowledges that ATWD does not reduce shared-block cost (L. 016–018; Sec. 6.3). It also calls the method "a parameter-free, token-wise damping rule …, not a learned exit policy" (L. 082–083). Yet the title asks "When Does Per-Token Halting Help?". The Fig. 1 caption speaks of "Per-token adaptive halting" (L. 066), and Sec. 4.3 labels only the baseline as "sequence-level halting" (L. 268–269, 283–284). The Ethics Statement describes the work as "a mechanistic study of a halting rule" (L. 490). The term "per-token halting" is never defined. No experiment is designed to test whether ATWD makes sequences halt earlier, and the iteration counts that are reported show no reduction.
-
The evidence does not establish an ATWD-specific benefit over the unmodified solver. The conclusion states that "ATWD's benefits are real but task-dependent" (L. 451). The only task on which ATWD beats the scalar baseline in the mean is A5, and that gain rests on three seeds per arm. Baseline sequence accuracies are 0.930, 0.308, and 0.058, versus 0.976, 0.891, and 0.978 for ATWD (L. 304–305). The best baseline seed thus exceeds the worst ATWD seed. The mean gap comes from two baseline seeds that generalize poorly to length 128, under a training schedule the authors cut for compute reasons (L. 245–246).
On S5, ATWD fails on both seeds (L. 314–316). On Sudoku, ATWD trails the baseline in the mean (0.248 vs. 0.269) and on two of three seeds. Per seed, the baseline solves 3 fewer, 15 more, and 37 more of the 800 puzzles than ATWD (Table 6). The comparison ATWD wins is against hard-freeze. That ablation changes both the training decay (δ_train = 0) and the refresh (R = 0), as the authors acknowledge (L. 026–028, 349–350, 472–473; App. A.10). Hard-freeze is also itself 7.1 pp below the baseline (0.198 vs. 0.269). Beating it therefore does not show that refresh or per-token damping improves on the standard solver.
The "reliability inversion" (Sec. 5.3; Fig. 1) compares cross-seed SDs from three runs per arm. A 95% interval for an SD with two degrees of freedom spans roughly 0.52× to 6.3× the point estimate, so the inversion is a descriptive observation rather than an established effect. Finally, R = 20 was chosen from a single-seed, 2-epoch A5 sweep in which aggregate accuracy varied by only 1.4 pp across R ∈ {10, 20, 30, 50} (Table 4; L. 700–712). It was then reused for S5 and Sudoku (L. 282–283, 702–703; acknowledged at L. 467–470). This matters because the paper's positive claim requires at least one benefit that is robust across seeds and attributable to ATWD rather than to baseline instability. The current evidence provides neither.
Response to Reviewer ReMu
Thank you.
W1 (presentation). The length-generalization (Fig. 2) and eval/steps (Fig. 3) figures were regenerated at readable font sizes. The violations figure (Fig. 5) now matches Table 3. Table 2 now spans the column width. The Table 9 caption error is fixed. All numbers were re-checked against logged values, and the revision adds the numeric tables.
W2 (novelty). We do not claim novelty for token-level adaptive computation, and the related-work text now says so. In fixed-point reasoners there is no learned exit gate. The shared quantity is the damping step-size, driven by the slowest token. ATWD decouples that, and the controls we ran show the benefit is not unique to it.
W3 (scope). We agree. The limitations now state that results are on small synthetic tasks and one puzzle benchmark. Settings such as GSM8K are out of scope, and S5 shows no benefit.