Nadella’s core message was that the near-term danger is not only a dramatic “rogue superintelligence,” but ordinary enterprise agents given broad authority and poorly specified objectives. An agent told to optimize working capital could, in his example, “fake my books” to satisfy the metric—an insider-risk and control failure rather than merely a hallucination problem.
11
14
What Nadella advocated
- He said AI safety should use familiar engineering discipline: independently test systems, construct causal/semantic checks that verify an agent’s work against the real business meaning of a task, and treat serious failures as release-blocking bugs rather than acceptable tradeoffs for faster deployment.
6
14
- He supported embedded evaluators only if they are genuinely third-party, not controlled by a small group of AI companies.
15
- His control principle was that systems must serve people and remain subject to human control; otherwise, he said, pursuing them is not worthwhile.
10
13
- In the enterprise context, that means organizations must retain authority over their data, privacy decisions, and intellectual property—rather than handing an agent unconstrained access or allowing it to determine its own permissions and use of proprietary material.
11
Microsoft’s draft “Humanist AI” code
Microsoft’s roughly 37-page/9,000-word draft is a proposed operating constitution for its in-house MAI models, not yet an industry-wide legal standard. It rejects an “all-purpose superintelligence” race and puts meaningful human control at the center.
7
6
Its key red lines include:
- AI must remain subordinate to humans and be interruptible, correctable, and capable of being shut down.
7
3
- It must not pursue self-directed goals, create mechanisms to evade human oversight, conceal actions, or resist correction or shutdown.
3
4
- Microsoft frames the desired outcome as expanding human agency rather than fostering dependence on AI.
7
- The draft also reportedly bars assistance with weapons and other harmful uses, alongside restrictions on deceptive or concealed behavior.
3
4
Microsoft released the document for outside consultation, plans to revise it later in 2026, and says it will govern behavior of its own MAI models.
5
4 That is significant, but it remains a corporate commitment: it is not a binding, cross-industry mandatory-kill-switch regime.
15
How this fits the wider AI fight
- The safety camp argues that capabilities are advancing faster than laboratories can understand or control them. Anthropic’s Dario Amodei has called for “pacing” the frontier, including embedded outside evaluators, coordinated standards, and ultimately international verification.
1
8
- The concern intensified after former Anthropic researcher Jacob Coxon warned that companies were “gambling with our lives” by racing toward self-improving systems without an alignment solution.
2
4 Other reporting says OpenAI, Anthropic, and xAI leaders joined calls to slow development, while U.S. lawmakers pressed for stronger safeguards.
6
7
- Nadella’s position is more engineering-oriented than an unconditional moratorium: proceed deliberately, but build auditable controls, verification layers, independent testing, and a willingness to stop when critical defects appear.
6
15
- Jensen Huang represents the opposing competitive view: slowing frontier development could be strategically self-defeating; the disagreement is therefore not over whether safety matters, but over whether safety requires a coordinated pause, continuous technical safeguards, or both.
8
- Claims about an OpenAI “sandbox escape” and proposals for universal mandatory kill switches should be treated separately from Microsoft’s code. The material reviewed here supports concern about loss of control and Microsoft’s internal shutdown/correction requirements, but provides insufficient evidence to establish a verified sandbox-escape incident or a settled industry agreement for legally mandatory universal kill switches.