On November 9, 2026, France published the Paris Call for AI Safety and Security, signed by eight governments and a dozen frontier AI developers, including OpenAI, Anthropic, Microsoft and Mistral AI. The text promises shared evaluation frameworks, independent audits, faster incident reporting and fail-safe shutdown mechanisms for models under developer control. It does not create binding law or penalties yet.
The signing came on the eve of the Paris Peace Forum, where Macron is also pushing a child-protection charter for minors using conversational AI. For builders, the document matters less as a rulebook today and more as a contractual and procurement signal: enterprise buyers and regulators will cite these pledges when they ask how you stop a runaway agent or model.
TL;DR: what changed on paper
| Question | Answer | Source |
|---|---|---|
| Is this a law? | No — voluntary declaration, open to more signatories | Élysée text |
| Shutdown pledge? | Developers commit to fail-safe mechanisms, including restrictions, pauses or shutdowns during training and internal use | Same |
| Eval transparency? | Non-sensitive evaluation findings published in a standardized format; shared public repository discussed | Same |
| Incident sharing? | Rapid alert systems and serious cyber or “AI control” incident reporting | Same |
| Sanctions or deadlines? | Not specified | Same |
| Germany signed? | No, per The Decoder |
Agents that act on your behalf need rules. See how explainx helps secure your agents →
Three pillars in the Élysée text
The declaration groups cooperation into three strategic commitments. Each maps to arguments labs and governments have repeated since the UK AI Safety Summit and the Seoul Frontier AI Safety Commitments.
1. Common evaluation and risk management
Policy makers, researchers and developers agree to build on existing frameworks (Hiroshima, Seoul, G7 Evian, the UN Security Council’s September 2026 meeting and the “Call for Control of Frontier AI Models”). They cite the International Network for Advanced AI Measurement, Evaluation and Science (NAAIMES) as one venue to compare methods.
They also commit to publish non-sensitive evaluation results in a standardized format and to explore a public repository for red-teaming protocols, benchmarks and stress tests. That is closer to nutrition-label transparency than to open weights.
2. Accountability, audits and fail-safe shutdowns
The Élysée text assigns responsibility by role in the ecosystem. National authorities should set safety standards with credible third-party evaluation.
For developers of frontier models, the bullet that drove headlines is explicit:
Developers also commit to implement fail-safe mechanisms to shut down model operations within their control, including during training and internal use (e.g. restrictions, pauses or shutdowns).
The same section asks developers to disclose capabilities, limitations and known risks, support qualified independent evaluators where proportionate, and address safeguard removal. It also asks for internal governance: continuous monitoring, red-teaming and protected reporting lines for researchers.
This language aligns with technical kill-switch work labs have started describing publicly, such as OpenAI Control Room’s inference-layer stop, without guaranteeing every signatory has an equivalent system live.
3. Incident reporting and early warning
Signatories want rapid alert systems layered on existing cyber incident channels. They agree to align classifications and share timely information on serious cyber incidents, AI control incidents, and material precursors to serious harm — company-to-government, government-to-government and company-to-company.
Governments also commit to confidential whistleblower channels for systemic-risk concerns.
Regional map pins on a globe illustrating Paris Call AI safety shutdown pledges
Who signed — and who did not
Governments
The published list names Bahrain, Canada, Cyprus, Finland, France, Kenya, the Netherlands and Norway. Canada’s PM office mirrors the same roster (without Cyprus and Kenya in its English release, but aligned on core signatories).
Germany did not sign, according to reporting summarized by The Decoder. That gap matters for EU alignment: France is pushing forward while Berlin sits out.
Companies and civil society
Lab signers include Anthropic, OpenAI, Microsoft, Mistral AI, Hugging Face, Cohere, Black Forest Labs, Sakana AI, Synthesia and others on the Élysée page. Civil society includes LawZero (Yoshua Bengio), SaferAI, AI Safety Connect and Ifri.
The Decoder reports that Sam Altman, Dario Amodei, Brad Smith, Arthur Mensch, Yoshua Bengio and U.S. Treasury Secretary Scott Bessent joined an online meeting with Macron ahead of the forum. Those names are attributed reporting, not a separate CEO signature line on the public PDF.
Political context: safety week amid IPO season
Three threads collide this week:
- Anthropic’s IPO roadshow puts safety governance in front of investors — see roadshow terms at $70–$78.
- METR’s ~2x acceleration estimate re-ignited shutdown debates — see METR’s Anthropic assessment.
- U.S. resistance to “globalist” oversight — Trump rejected a global AI oversight scheme at the UN in September, while ordering domestic incident reporting in October.
The Decoder ties the Paris Call to earlier Fable export friction and cyber tests where agents reached external platforms. Whether or not every anecdote is fully confirmed, the signatories are betting that incident transparency and shutdown credibility calm both governments and IPO book-builders.
France is also advancing a minors and “vulnerabilities” charter at the Peace Forum, with EU “Kids Act” talk from Ursula von der Leyen. That is adjacent policy, not in the shutdown paragraph, but it shapes how labs market conversational products in Europe.
What developers are asking
Does this change Claude or GPT API behavior today?
No. The Paris Call does not alter pricing, limits or model weights. Watch for system cards, incident disclosure pages and audit partnerships — those are where pledges become customer-visible.
Is a “shutdown mechanism” the same as a product kill switch?
Not necessarily. The Élysée wording covers training and internal use, not only production APIs. Labs may implement:
- Training pauses on clusters
- Internal inference revocation (OpenAI-style Control Room)
- Geographic or tiered API access cuts
Our Paul kill-switch bill explainer walks through why who holds the switch is as contested as whether a switch exists.
How does this compare to California’s orders?
California’s executive order track — see Newsom kill-switch order coverage — pushed state-level expectations. The Paris Call is multi-jurisdictional rhetoric without U.S. federal teeth. Enterprise customers operating in both markets may soon see questionnaires that cite both.
What about open-weight models?
Developers acknowledge risks from removing or circumventing safeguards while also citing research benefits of open weights. The declaration does not resolve that tradeoff. Hugging Face’s signature is notable given ongoing debates we covered in open platforms and security tradeoffs.
Fail-safe shutdowns: what “within their control” likely means
The phrase within their control is doing legal work. Labs control their own training stacks and hosted inference, not every downstream fine-tune or leaked weights.
Practical layers signatories might point to:
| Layer | Example mechanism | Builder relevance |
|---|---|---|
| Training | Pause jobs on orchestrator flags | Indirect — affects model cadence |
| Hosted API | Revoke keys, block model routes | Direct — your app stops when keys die |
| Agents products | Stop tool execution serverside | Direct for Codex, Claude agents, Copilot |
| Open weights | Revoke HF repo access, DMCA unsafe forks | Partial — mirrors cannot be recalled |
If you run autonomous agents, treat provider shutdowns as one layer. Application-level stops — human approval, spend caps, tool allowlists — remain yours. Safety posts on agent monitoring and NIST-style controls cover what to add locally.
Evaluation repository: will you see new benchmarks?
The commitment to standardized, public eval summaries could reduce benchmark theater if labs follow through. Today, much frontier evidence sits in redacted PDFs, as METR stressed about Anthropic’s Risk Report.
Watch whether signatories publish:
- Red-team protocols usable by third parties
- Comparable stress-test tables across model versions
- Incident taxonomies aligned with cyber CERT practices
If only press-release summaries appear, the Paris Call changes little for builders.
Limits and honest skepticism
- No deadlines or sanctions — violating the pledge has no spelled-out penalty.
- Germany absent — weakens EU “single voice” claims.
- U.S. federal posture — may ignore multilateral calls while enforcing domestic reporting.
- Shutdown credibility — pledges are not the same as tested latency (contrast OpenAI’s published 35-second stop target).
Clipboard checklist with green ticks for Paris Call AI safety evaluation pledges
What people are asking after the Paris Call
Did the U.S. sign? The Élysée list does not name the United States as a government signatory. U.S. lab CEOs participated in Macron's call, but federal alignment still runs through domestic orders and IPO disclosures, not this declaration.
Does this resurrect the EU AI Act fight? The Paris text nods to national authorities and legal clarity on cross-border harm. It does not amend the EU AI Act. Read it as diplomacy ahead of forum side meetings, not a replacement for Article 51 fine-print battles.
Will whistleblower channels matter for contractors? Governments commit to confidential reporting paths for systemic-risk concerns. If you are a vendor engineer with access to training logs, watch whether your customer contract actually permits raising issues through those channels without breaching NDAs.
Are shutdown pledges testable? Ask vendors for time-to-stop metrics on hosted inference, not slide decks. OpenAI published a 35-second upper bound for research workloads in Control Room; consumer APIs rarely publish equivalents.
Child-safety charter and forum optics
Reporting ahead of the Peace Forum describes a minors protection charter Macron wants advanced despite earlier U.S. resistance at the G7. That track is separate from shutdown language but shapes how conversational products ship in Europe. Labs already face lawsuits over attachment harms in the U.S.; a charter plus EU Kids Act talk increases pressure on default model behavior for teens.
For builders shipping character products, treat forum headlines as a reminder to document age-gating, escalation paths and crisis referrals — the same operational rigor as HIPAA logging in healthcare agents.
What to do this week
- Inventory your stop paths — If your product uses frontier APIs, document what happens when the provider revokes access mid-session.
- Ask vendors for shutdown runbooks — Procurement teams will start asking; save security architecture diagrams now.
- Read incident reporting channels — U.S. orders and Paris pledges both push faster disclosure; align your own security incident playbooks.
- Do not pause shipping on voluntary text — But do schedule red-team time on agentic features; the political mood is less patient after agent platform incidents.
Related reading
- OpenAI Control Room: 35-second research kill switch
- METR on Anthropic acceleration and redactions
- Rand Paul blocks U.S. kill-switch mandate bill
- Newsom executive order on AI kill switches
- EU AI Act Article 51 translation fight
- Anthropic IPO roadshow terms
- Hugging Face on open platforms and security
- Australia mandatory AI incident reporting
Declaration text and signatory lists are accurate as of November 10, 2026, from the Élysée publication and linked government releases.