1. By the paper's own Table 6, a trivial category filter matches the main controllability result (RQ2, Table 2).
- The feedback is derived from the target's category path. The target is therefore always inside the "T3: Fine + Suppression" compatible set.
- Table 6 reports a median of 144 compatible items, so at least half of the cases have ≤ 144 candidates.
- Returning 10 uniformly random compatible items thus gives R@10 ≥ 0.5 × 10/144 ≈ 0.035. That already matches ControlRec's T3 R@10 of 0.0344.
- The true value of this random baseline is necessarily higher. Every case with fewer than 144 compatible items (the minimum is 2) contributes more than 10/144. It could plausibly exceed even ControlRec + Tag Reranking (0.0615, Table 11).
- A filter that ranks the compatible items by a history-only model's full-catalog score (HSTU or LLaDA-Rec with a hard category constraint), or by popularity, should be stronger still.
The "LLaDA-Rec + Tag Reranking" reference only reorders candidates that were already generated, so it is not this baseline. Without "history-only scorer + hard category filter over the full catalog" and "random/popular within the compatible set", RQ2 does not show that the intent machinery uses the feedback well. As it stands, it suggests the feedback is used less effectively than a filter would use it. If Table 6 is computed on a different population than the 43,577 cases, please say so.
2. The ReDial control metrics are largely satisfied by construction, and the baselines lack the same structure. ControlRec receives a parsed, catalog-validated genre constraint and applies hard logit suppression. KBRD, KGSF, BARCOR, UniCRS and the LLMs receive raw dialogue. Sat.@10 ≈ 0.99 and Viol.@10 ≈ 0.01 therefore mostly reflect the deterministic constraint rather than learned control. Fair comparisons would be each baseline with the same parsed-genre filter, or ControlRec's parser combined with a simple filter on a non-diffusion recommender. The test sets are small (175/150/150 instances) and come without CIs. The 0.2914 vs. 0.2571 R@10 gap is about 6 instances, and All-Req 0.98 vs. 0.967 is 2 instances.
3. The Amazon hard-case baselines look non-functional or structurally disadvantaged.
- KGSF, BARCOR and UniCRS have T0 R@10 ≈ 0.0001. These are KG- and ReDial-oriented CRSs. The paper does not describe how they were adapted to Amazon industrial products: which knowledge graph, and which item vocabulary.
- The LLM-agent baselines get worse with feedback (Llama-3-8B: 0.0087 → 0.0037 at T1).
- B.1 says the agents rank "prepared Top-100 candidates". If those candidates come from HSTU, the target is absent by construction, because the subset consists of HSTU misses@100.
Please specify each baseline's candidate pool and adaptation.
4. Where the dialogue-free gains come from is not ablated. The RQ1 improvements over LLaDA-Rec (e.g., R@1 0.0098 → 0.0115 on Industrial) could come from any of three sources:
- (a) the extra multi-task alignment pretraining (MaskItem/NextItem/Match/Rank, with item text);
- (b) four-branch decoding with merging, which is effectively a test-time ensemble;
- (c) the prototype "intents" themselves.
The Fig. 3 ablation covers only the hard-case dialogue protocol. Please ablate RQ1 and add a compute-matched LLaDA-Rec (four decoding runs or beam groups, merged). Two further points:
- The seed standard deviations (±0.00005 on R@1) suggest that only a small module varies across seeds. Is the backbone a single fixed checkpoint?
- A.7 suggests the baseline numbers are copied from prior work, e.g. LLaDA-Rec (Shi et al., 2025). If so, please confirm identical splits and preprocessing.
5. The free-form-language claim is not what is evaluated. The abstract and contributions emphasize "freely expressed natural-language requests". The evaluated pipeline, however, collapses every utterance into a validated catalog category ID. The free-form mechanism shown in the demo (B.6: matching requests against titles and plot summaries, then aggregating into SID logits) is a different mechanism with no quantitative evaluation. The parser accuracy in B.4 is measured on synthetic, category-level trajectories. The "real case exploratory user study" in B.6 is three hand-picked examples, not a user study.
6. The novelty is mostly integration, and the related work misses directly relevant lines.
- Per-interest retrieval with weighted aggregation is ComiRec's aggregation module (Cen et al., 2020). The paper cites ComiRec but does not discuss this overlap.
- The related work omits user-controllable, editable and scrutable recommendation: UCRS (Wang et al., SIGIR 2022), LACE with editable user profiles (Mysore et al., SIGIR 2023), and scrutable user models (Balog et al., SIGIR 2019).
- Parsing language into structured operations is common in tool-using recommender agents, e.g. InteRecAgent, which the paper times in B.1.
- Suppressing negative attributes through logits is standard constrained decoding.
"We first introduce a unified intent-mediated formulation" and "we first achieve intent-guided parallel diffusion generation under conversational control" overclaim.
7. The necessity of the Semantic Alignment Adapter is unclear. At evaluation time the parser outputs a catalog category c, and the adapter only maps c's text to (z(c), B(c)). A training-free alternative would derive B(c) from the empirical SID-code distribution of items in c. This alternative is not compared, and the paper does not state what replaces the adapter in "w/o Align". SID codes are also shared across categories, so suppressing a category's codes can suppress unrelated items. The collateral recall loss on non-suppressed items should be measured.
Summary of additional results and request for feedback
Dear Reviewers 3ccz, NBGy, and pKhr,
As the author–reviewer discussion closes on November 18 and we have not yet received any follow-up feedback, we briefly summarize the clarifications and additional results addressing your concerns.
We would appreciate your feedback on whether these responses address your concerns. If any issues remain, please let us know so that we can clarify them before the discussion closes. If the additional evidence changes your assessment, we would be grateful if you could update your review accordingly.
Thank you for your time and consideration.