Nearly cut
A Google harness claims 218 of 222 Codeforces problems and 71 per cent on research-level theorems, on Google’s models
Kept, although every number is the authors’ own on their employer’s models, because the harness ships inside a Google product as a named pattern a builder can turn on.
Six authors including Vahab Mirrokni report that their harness solves 218 out of 222 Codeforces problems with Gemini 3.1 Pro and execution feedback.
The same harness, Stellar Colosseum, scores 71.0 per cent on TCS-Bench, theorem-proving tasks drawn from FOCS, STOC and SODA papers, using Gemini 3.1 Pro with Gemini 3.7 Flash, against no stated baseline for either figure. The paper nearly cut it: the arXiv page lists no affiliations, the evaluations are the authors’ own, and no independent run exists.
It stayed for one sentence in the abstract: the workflow “has also been integrated into Google Antigravity’s Teamwork framework as the Long Proof pattern”. That makes it a product setting rather than a paper, and the mechanism is worth having in words. Colosseum explores strategies before it writes a proof, uses “a readiness gate to decide when a route is mature enough to decompose”, represents the plan as section-level subproblems, and routes verifier findings back to the affected section. Candidates are generated in parallel, attacked with targeted falsification, and merged by what the authors call overlapping random-sample tree aggregation.
The authors also claim new results on open problems from FOCS and JMLR papers, which this paper has not read and cannot assess.
What a builder gets is a name for a pattern, and a number to demand from anyone selling it on a model that is not Gemini.
What it changes Nothing to switch on this week unless you are in Antigravity. If you build long-horizon proof or planning agents, the readiness gate and the verifier-to-section routing are the two ideas to steal.
All figures are the authors’ own on Google models; the arXiv page lists no affiliations, and the paper infers Google from the Antigravity integration the abstract states. TCS-Bench and the Codeforces set have not been run independently.
Publisher's claim, unverified