Google DeepMind will start publishing its safety checks and capability-based safeguards, having already internal checks and balances.

No deadline given. True: Google DeepMind began publishing documents that set out its safety checks or safeguards tied to model capabilities, for example a published safety framework, dangerous-capability evaluation results or model-card safety sections. Its contents need not meet any quality bar, but the document itself must describe such checks or safeguards; merely calling something safety-related is not enough. Mostly true: it published such material but only partially, such as evaluation results without the safeguard framework, or the reverse. Mostly false: it made only general statements of principle, with no description of specific checks or safeguards. False: dated evidence shows it declined to publish, or later statements confirm that nothing of this kind was published.

Set before the research began.

1. E1 Introducing the Frontier Safety Framework Google DeepMind · 17 May 2024 Own record

   “Today, we are introducing our Frontier Safety Framework — a set of protocols for proactively identifying future AI capabilities that could cause severe harm and putting in place mechanisms to detect and mitigate them.”

2. E2 Evaluating Frontier Models for Dangerous Capabilities Google DeepMind · 21 March 2024 Own record

   “We do not find evidence of strong dangerous capabilities in the models we evaluated, but we flag early warning signs.”

3. E3 Gemini 3.7 Flash Frontier Safety Framework Report Google DeepMind · August 2026 Own record

   “We released our Frontier Safety Framework (FSF) (v1) in May 2024 and updated it in February 2025 (v2),”

4. E4 Gemini 4 Argon - Model Card Google DeepMind · October 2026 Own record

   “Cybersecurity CCL: We cannot rule out that Gemini 4 Argon has reached this CCL, and we therefore developed a safety case for its cyberoffensive capabilities that we assess lower risk to below the cybersecurity CCL level.”

The claim resolves true: Google DeepMind published both parts the criteria call for. In March 2024 it published dangerous-capability evaluation results (E2). In May 2024 it published a Frontier Safety Framework of protocols for spotting capabilities that could cause severe harm and putting mitigations in place (E1). Later records show the framework was updated in February 2025 (E3), and the Gemini 4 Argon model card includes a cybersecurity CCL assessment and a safety case for the model's cyberoffensive capabilities (E4). All of these are the subject's own publications, but they are the published deliverables themselves. There was no deadline, so on_time is null.