AI companies pledge shutdown controls in Paris declaration without binding enforcement
The agreement pairs developer safeguards with shared testing and incident reporting. One signatory wants governments—not just companies—to hold suspension powers.
Loading page…
The agreement pairs developer safeguards with shared testing and incident reporting. One signatory wants governments—not just companies—to hold suspension powers.
Listen to this story
Signatories to the Paris Call for AI Safety and Security are promising to pause or shut down training and internal model use when needed, but the November 9, 2026, declaration has no deadlines, sanctions or international enforcement. It relies on national oversight and voluntary company controls, not a universal stop mechanism. CeSIA, which signed, says public authorities still need common risk thresholds, guaranteed evaluator access and power to suspend development or deployment—conditions that will help determine whether the pledge can constrain high-risk systems in practice.
Companies also commit to real-time capability monitoring, adversarial testing, defined safety responsibilities and protected internal reporting lines.
Planned shared frontier-model evaluations target cyber misuse and autonomy or loss-of-control risks, with non-sensitive findings going into a public repository.
Signatories plan to share serious cyber and AI-control incidents, including significant warning signals, and work toward common classifications.
OpenAI, Anthropic, Microsoft and other AI developers signed a Paris declaration on November 9, 2026, committing to controls that can interrupt models under their control. But the Paris Call for AI Safety and Security creates no binding international enforcement system—and one civil-society signatory is already calling for public powers to suspend development or deployment.
Governments including France, Canada, Finland, Norway and the Netherlands joined companies and civil-society organizations in signing. The political commitment sets neither deadlines nor sanctions. Its published supporter list remains open to endorsements and is being updated.
CeSIA, the Center for AI Security, signed the declaration and welcomed it as a first step. In its November 10 response, it identified three missing guarantees: common risk thresholds, assured model access for evaluators and public authorities, and a suspension mechanism controlled by public authorities.
The declaration does envisage government oversight through safety standards established or recognized by national authorities. CeSIA wants a more specific framework: mandatory independent evaluations and common risk thresholds that determine whether development and deployment may continue.
These decisions must rest with public authorities, who must be able to rely on independent evaluations with guaranteed access to models.
Charbel-Raphaël Ségerie, CeSIA executive director, on suspending development or abandoning deployment
The shutdown commitment covers model operations within a developer’s control, including training and internal use. The declaration gives restrictions, pauses and shutdowns as examples of fail-safe mechanisms. It is a promise to interrupt operations developers control, not a universal switch for every use of their models.
Developers also commit to disclosing capabilities, limitations and known risks. Support for qualified independent evaluation is conditional: it should be appropriate, proportionate to risk and consistent with existing practices and arrangements.
Inside companies, the text calls for continuous risk management, real-time monitoring of emerging capabilities and rigorous adversarial testing, often called red-teaming. Developers commit to working toward governance with defined responsibilities, adequate resources and independent oversight, alongside reporting lines that protect internal researchers.
A proposed common evaluation framework would use shared standards, tools and methods for frontier models—the most advanced AI systems. Its focus includes dangerous cyber misuse and risks from growing autonomy or models behaving contrary to intended goals, including loss of control.
Signatories agree to publish non-sensitive evaluation findings in a standardized format and create a publicly accessible shared repository. Potential contents include adversarial-testing protocols, benchmarking tools, risk assessments and stress-test results.
Incident cooperation would extend beyond completed harm to significant warning signals. The text calls for timely sharing of serious cyber and AI-control incidents and work toward common incident classifications. Public officials also commit to secure, confidential channels for whistleblowers to raise reasonably grounded systemic-risk concerns without fear of legal or professional retaliation.
Loading discussion...
Join the conversation
Explain what would make that power necessary—or too easy to misuse.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.