- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper studies source-free latent reuse: a model encodes a source before receiving a later request, exports a compact representation, and then answers requests after source tokens, source KV caches, old positions, and non-exported runtime states have been removed. Semantic Interface Distillation (SID) combines a query-independent slot resampler, a router supervised by the effect of removing individual slots on teacher agreement, and a query-conditioned temporary workspace used by a fresh consumer. Evaluation covers delayed actions in Register-World, evidence deletion and replacement in Evidence Inference, and document/hypothesis swaps in ContractNLI. The reported results favor SID over interfaces adapted to the same reset setting, with the largest improvements in evidence-branch joint agreement. However, conflicting descriptions of the status of numerical results and incomplete specification of the instantiated interfaces prevent a firm assessment of these gains.
Critical strengths
-
A useful and explicitly constrained evaluation problem. Section 3 distinguishes stored information from what a new consumer can execute after the original runtime is removed. Figure 2 separates linear readability, single-state execution, and execution with richer runtime inputs. The document/hypothesis and evidence-edit interventions test more than accuracy on a single original query. This is consequential because a representation that supports one immediate answer need not support later reuse.
-
A coherent architecture with encouraging reported branch-reuse gains. The slot bank, removal-based routing supervision, and temporary workspace address different aspects of the reset problem. In Table 2, SID improves eight-branch joint agreement from 37.95% for ICAE-8 to 52.33%, while also improving natural-task macro-F1 from 75.63% to 78.04%. Table 4 reports drops from removing counterfactual routing and rehydration. If confirmed, these results support a useful contribution beyond simply storing the final hidden state. The paper also appropriately states that clinical edit scores measure teacher agreement rather than independently established clinical correctness.
Critical weaknesses
Please refer to questions.
Questions for authors
-
Clarification of measured results: Which entries in Tables 6 and 7 are actual measurements, and on which splits? Why do the non-default K/m values match the entries identified as planned reference values, and why do the default development values match Table 2? Please provide corrected tables and the corresponding run/configuration records for the values used to select the final interface.
-
Clarification of interface budgets: What do “-80” and “SID-Hybrid” mean in the ContractNLI experiment? Please specify persistent states, total stored bytes, per-request states, and trainable components for SID and each comparator.
2 comments
Thanks for the response
Thanks for the response. It addressed my questions. I would like to keep my score..
Thank Reviewer for carefully identifying these ambiguities in the tables and interface definitions.
1. Clarification of measured results
All reported entries in Tables 6 and 7 are based on executed experiments. The note stating that some values were planned reference values came from an earlier AI-generated table template with blank result cells. After the measured results were inserted, this outdated note was inadvertently retained.
The non-default rows in Table 6 are measured sensitivity results for the Evidence Inference configuration sweep. Table 7 intentionally reuses the corresponding measured quality results and reports their capacity and timing information. Thus, matching K/m values across the two tables refer to the same underlying runs; they do not represent planned reference values or duplicated experiments.
The default quality row references the final configuration reported in Table 2. It is included to show the performance of the selected interface alongside the sensitivity and efficiency results, rather than to represent an additional development run. The default row in Table 7 follows the same convention. We have uploaded the run logs together with the code.
2. Clarification of interface budgets
The suffix “-80” denotes the original reference versions of Gist, ICAE, xRAG, and SFI that use 80 latent states/tokens. It is not the same budget as our contract-adapted comparisons. Under the Qwen3-0.6B hidden width of 1,024 and BF16 storage, 80 persistent states correspond to 160 KiB. These reference versions pass the 80-state packet to their original decoder interface and do not use the matched m=4, J=4 SID rehydration protocol.
The suffix “-8” denotes our contract-adapted eight-state implementations. These methods use the same hard-reset consumer wrapper, routing budget (m=4), scratch budget (J=4), and task head. Thus, their persistent payload is 16 KiB, while each request routes four persistent states and constructs five transient decoder positions: four scratch states plus one query-conditioned state.