Deep Review: who checks the AI-written document?

Transcript

The original narration, preserved as published. Relative dates refer to the episode’s coverage window.

Who checks a technical document after A I helps write it? Google opened Deep Review to the public on October fourteenth. It reviews complex documents for logical gaps, mathematical mistakes, and claims that need stronger support.

The system divides a document into sections, assigns different reasoning budgets, and runs specialized checks in parallel. A final agent combines the reports and checks consistency across sections. That is a workflow built around review, rather than one request for a summary.

Google says its earlier Paper Assistant Tool gave optional feedback on more than sixteen thousand manuscripts. That feedback was separate from official conference decisions. The new public service initially accepts P D F and plain text. Multi file input is still coming.

Each user gets two complimentary reviews per week, with a Gemini API key for higher limits. Google says uploads are not used for model training, but are stored for one year to display in the interface. Check those terms before sending a sensitive draft.

The useful output is a set of claims to investigate. Follow the evidence, check the equations, and decide which criticism holds up. Automated critique can widen access to detailed feedback; it does not transfer responsibility for the final document.