antistatic.exchange
Register Log in

Google DeepMind safety capability thresholds

By end of 2026 By end of 2026
2.0%
Adjust month-by-month → →
By end of 2027 By end of 2027
17.6%
Adjust month-by-month → →
By end of 2028 By end of 2028
37.7%
Adjust month-by-month → →
By end of 2029 By end of 2029
57.2%
Adjust month-by-month → →
By end of 2030 By end of 2030
71.6%
Adjust month-by-month → →
Log in to submit a forecast.

3 comments

Log in to comment.

1

The Gemini 4 Argon Safety & Security Report (October 13) includes an audit of whether AI is speeding up Google's own AI research. Google fitted an internal General Capability Index across 123 models and 92 benchmarks and compared the pace of frontier Gemini progress before and after 1 April 2026: 0.091 points per month before (95% CI 0.071–0.108) and 0.118 after (0.053–0.171), a difference it calls not statistically significant. Argon scores above trend, which Google attributes to more organisational investment and training compute rather than AI-driven acceleration. On automation, most production code at Google DeepMind is now over 75% AI-written, and fully delegated pull requests rose from 7.5% in April to 11.9% in September 2026; about 88% still need multi-turn human steering or human-written code. The report marks ML R&D Acceleration Level 1 as "CCL not reached". Gemini 4 Argon Safety & Security Report, §3.4.2, pp. 74–77

1

Google’s November 13 post reports Argon /teamwork achieved 4.09× geometric-mean speedups across 17 JAXBench kernels and 2.99× across seven hand-optimized vLLM TPU-inference kernels. Its 23-second proxy evaluators were checked against full hardware runs. source

1

Google omitted an Argon research-engineering benchmark point estimate for the original task subset because infrastructure timeouts interrupted runs. Even treating every unfinished run as successful left it below Google's 90% cutoff. Report, p. 67