Use this to reason about how ICML reviewers and ACs will process a submission. The point is not to forecast acceptance by score folklore; it is to identify the decision issue and response strategy.
ICML ACs synthesize conflicts into a meta-review, so the useful question is which dimension an AC can defend a decision on.
| Dimension | What a reviewer cites | What an AC can act on |
|---|---|---|
| Soundness | Broken proof, untuned baseline, leakage | Strong reject anchor; hard to rebut without new evidence |
| Originality | Overlap with prior or concurrent work | Reject anchor unless delta is reframed |
| Significance | Narrow gain, no mechanism | Borderline; rebuttal can reframe scope |
| Clarity | Buried contribution, dense columns | Often fixable; weakest reject basis alone |
The optimizer paper draws one champion citing the convergence theorem, one skeptic citing an untuned Adam baseline, and one borderline reviewer citing clarity. The AC-quotable issue is the baseline soundness concern, not clarity, so the response strategy concentrates the single discussion round on the tuned-baseline table. Because accepted reviews and discussion become public, the authors keep the tone measured. If the paper also flagged Policy A LLM-review handling, confirm that choice is consistent so it does not surface as a procedural risk. Verify the per-paper review count and policy labels against the current cycle rather than assuming the prior year's setup.
[Likely review pattern] supportive / split / skeptical
[AC decision issue] <one issue>
[Procedural risks] <LLM policy / reciprocal reviewer / ethics / anonymity / none>
[Response posture] clarify / add small result / concede / reroute
[Public-record concern] <what will be visible if accepted>