In this analysis
Helping an author improve a manuscript and deciding whether a venue should accept it are different responsibilities, even when they examine the same document.
The route from the optional ICML Paper Assistant Tool pilot to public Deep Review helps separate two ideas often merged in discussion: giving an author useful criticism and exercising the authority of a scientific review process.
The dated path
-
2026-01-14: ICML Paper Assistant Tool pilot.
-
2026-06-26: Towards Automating Scientific Review with Google’s Paper Assistant Tool.
-
2026-10-14: Google publicly releases Deep Review.
The same finding can serve different roles
A possible error can help an author revise a draft without determining how an institution should evaluate the final submission. An institutional decision also concerns scope, standards, competing evidence and the responsibilities of the venue. Our retrospective interpretation is that author assistance became a practical entry point because it offers a bounded role. The author can investigate a finding and choose a revision while the official process retains its own procedures and decision makers.
Why the earlier pilot boundary matters
An optional feedback programme creates a different evidence setting from an official review. Participation, draft maturity and willingness to act on suggestions can influence what is observed. A successful assistance experiment therefore supports a claim about that role under those conditions. It should not silently become proof that automated judgments can replace a venue’s review. The dated ICML pilot explicitly supplies context for this distinction; the later public release broadens access without erasing the difference between assistance and authority.
A counterfactual with unchanged feedback
Imagine identical technical comments delivered in two settings. In one, the author uses them privately to improve a draft. In the other, they are treated as decisive evidence for an institutional outcome. The comments have not changed, but the consequences and required safeguards have. This comparison shows why evaluating comment usefulness is only part of evaluating a review system. The workflow must also establish who checks disputed findings, what evidence is available and how a mistaken objection can be challenged.
What infrastructure should preserve
A review artifact should identify the document version, the role of the feedback and the evidence associated with each finding. Exporting a private assistance report should not automatically give it the appearance of an official verdict. This is a proposed design implication, not a claim about every public Deep Review interface. The historical lesson is that new AI capability can enter an established institution through a carefully bounded task. Its wider adoption remains a question of role definition and evidence, rather than a simple extension of model accuracy.
Technical background
Related engineering context: Evaluation scope; Artifact provenance.