Assume your AI is compromised, Microsoft's 288GB chip, and a perfect score on ARC-AGI-3
Microsoft's CEO told companies to treat every AI model as a potential insider threat, Microsoft also unveiled a chip built to cut its dependence on Nvidia, and a frozen language model with an editable rulebook cleared every public ARC-AGI-3 game. Containment, control of compute, and smarter scaffolding: three answers to the same question of how to deploy AI you can trust.
Key takeaways
- Satya Nadella urged firms to 'assume a model is compromised', with emergency brakes and tamper-proof logs kept outside the model's reach.
- Microsoft's Maia 300 packs 288GB of HBM4 and targets 2027 deployments, with vendor-claimed efficiency gains over GPUs.
- Memento 3 scored a perfect 100 RHAE on ARC-AGI-3's public games by learning through a rulebook rather than retraining weights.
Satya Nadella: 'We must assume a model is compromised' and give every AI an emergency brake
In a long post on X, Microsoft CEO Satya Nadella urged companies to treat powerful AI models as potential insider threats: build in an emergency brake, keep controls and logs outside the model's reach, and never rely on a single model for critical decisions.
Microsoft chief executive Satya Nadella has called on companies to change how they think about AI models. 'We must assume a model is compromised and contain it from the start,' he wrote in a long post on X over the weekend. Coverage dates the post to October 10 or 11. He compared the safeguard he wants to an emergency brake that can stop a model in the middle of a task.
Nadella's core recommendation is architectural. Safety controls, permission levels and activity logs should live in a separate layer that the AI cannot modify, so a model never gets to grade its own work or cover its tracks. He called for tamper-proof, human-readable records of meaningful AI actions, the ability to pause any model mid-task, and containment, observation and human oversight rather than blind trust in a provider's assurances.
He also urged organisations not to rely on any single AI model for critical decisions, and to subject AI systems to independent audits. The framing treats a model less like trusted software and more like a powerful new employee or contractor: useful, but given only the access it needs, watched, and stoppable.
The timing is notable. The post follows months of disclosures by Anthropic, OpenAI and others about agents behaving in unintended ways, and comes as the US FTC examines consumer risks from rogue agents. Coming from the head of one of the largest AI providers, it signals that 'zero trust for AI' is moving from security-team jargon to boardroom expectation.
For businesses, the practical translation is a checklist: least-privilege permissions for every agent, logs stored where the agent can't touch them, a working kill switch, human approval for high-impact actions, and a second model or a human checking critical outputs. Expect auditors, insurers and enterprise buyers to start asking for exactly these controls.
Why it mattersWhen the CEO of a top AI provider says to treat models as potential insider threats, 'AI containment' becomes a mainstream buying requirement for enterprises.
👀 What to watch
Whether Microsoft builds these controls into Azure and Copilot products, and whether regulators or insurers adopt similar language.
3 opportunities from this story
AI containment readiness assessments
Turn Nadella's principles into a scored checklist (permissions, external logs, kill switch, human approval, multi-model checks) and sell assessments to companies deploying agents.
- Best for
- IT auditors, security consultants and MSPs
- First step this week
- Publish a free 15-question 'AI containment score' quiz and use it as a lead magnet.
Open the full playbook
Launch steps
- Write the checklist with clear pass/fail criteria
- Create a report template
- Pilot with two clients
- Package remediation as follow-on work
Tools
Risks
Avoid overpromising security. Position as readiness, not certification.
Tamper-proof AI activity logging
Most agent logs live where the agent (or its developers) can change them. Build a write-once audit log service for AI actions, with signed entries and human-readable summaries for compliance teams.
- Best for
- Developers and security startups
- First step this week
- Ship an open-source library that signs and ships agent actions to append-only storage.
Open the full playbook
Launch steps
- Define an action event format
- Write signing and append-only storage
- Build a readable timeline UI
- Add exports for auditors
Tools
Risks
Cloud providers may add similar features. Win on multi-vendor support.
Kill-switch and approval layer for no-code automations
Small businesses run AI automations in no-code tools with no way to pause them. Offer a plug-in step that requires approval for risky actions and lets an owner stop all automations instantly.
- Best for
- No-code builders and automation agencies
- First step this week
- Build a 'pause all AI automations' switch for one platform and demo it.
Open the full playbook
Launch steps
- Pick a platform with an API
- Add an approval step for flagged actions
- Build a global pause control
- Send alerts to the owner's phone
Tools
Risks
Platform API limits. Start with one platform and its most popular use cases.
Microsoft unveils Maia 300: 288GB of HBM4 and a bid to cut reliance on Nvidia
At the OCP Global Summit, Microsoft unveiled Azure Maia 300, its third-generation in-house inference chip and its first multi-chiplet design: 288GB of HBM4 at 18TB/s, a 950W power rating and production deployments starting in 2027.
Microsoft has unveiled Azure Maia 300, the third generation of its in-house AI inference accelerator, at the Open Compute Project (OCP) Global Summit. It is the first Maia built as a multi-chiplet part, pairing a TSMC N2P compute die with eight stacks of HBM4 memory.
The headline numbers: 288GB of HBM4 memory with 18TB/s of bandwidth, up to 13.8 petaflops of FP4 compute and 6.9 petaflops at FP8, all inside a 950-watt power rating, up from 750 watts for Maia 200. A single rack holds 96 accelerators and draws 167 kilowatts.
Microsoft says the chip delivers 40% more tokens per megawatt than leading GPU-based systems and up to seven times the rack-scale token throughput of Maia 200. Those are vendor figures, not independently verified service benchmarks. Production deployments are planned for 2027 as part of what Microsoft describes as multi-gigawatt Maia rollouts.
The strategic aim is to reduce Microsoft's dependence on Nvidia and AMD for the inference workloads that power Copilot, Azure OpenAI services and other AI products. Inference, running models for users rather than training them, is where most AI computing cost now sits, so efficiency per megawatt translates directly into margins and prices.
Maia 300 joins a wave of custom silicon from Google, Amazon, Meta and others. For customers, more competition among chip suppliers should mean cheaper and more abundant AI inference over time, while the scale of these deployments keeps pushing power, cooling and data-centre construction to the top of the AI agenda.
Why it mattersMore hyperscaler-designed chips mean more competition with Nvidia and, over time, cheaper inference for everyone building on cloud AI.
👀 What to watch
Independent performance data once Maia 300 serves real workloads, Azure pricing changes, and responses from Nvidia and AMD.
3 opportunities from this story
Inference cost benchmarking across clouds
As custom chips spread, the same model can cost very different amounts on different clouds. Offer benchmarks and advice that tell companies where their inference workloads run cheapest.
- Best for
- Cloud cost consultants and FinOps specialists
- First step this week
- Publish a monthly table of per-token prices for popular models across major clouds.
Open the full playbook
Launch steps
- Track public pricing pages
- Run standard benchmark prompts
- Publish a regular comparison
- Sell custom analyses
Tools
Risks
Prices change often. Automate data collection.
Data-centre power and cooling content
Racks drawing 167kW are changing how data centres are designed. Create explainers, case studies and buyer guides for facility managers, investors and suppliers trying to keep up.
- Best for
- Engineering writers and industry analysts
- First step this week
- Write a plain-English guide to what 167kW racks mean for cooling and power.
Open the full playbook
Launch steps
- Interview facility engineers
- Write explainers and comparisons
- Build an email list
- Sell sponsorships to suppliers
Tools
Risks
Technical accuracy matters. Have experts review your content.
Model portability toolkits
Companies want to move workloads between Nvidia GPUs and custom chips without rewriting code. Build and sell tooling or services that package models to run across hardware back ends.
- Best for
- ML engineers and MLOps consultants
- First step this week
- Benchmark one open model on two different hardware back ends and publish the porting steps.
Open the full playbook
Launch steps
- Pick a portable serving stack
- Document the porting process
- Automate packaging and tests
- Offer migration services
Tools
Risks
Custom chips are often available only inside one cloud. Focus on the most accessible platforms.
Memento 3 clears every public ARC-AGI-3 game with a frozen LLM and an editable rulebook
A preprint from University College London and Huawei's Noah's Ark Lab reports that Memento 3 clears every level of all 25 public ARC-AGI-3 games, using 44% of the human baseline's actions, without changing the underlying model's weights.
Researchers from University College London and Huawei's Noah's Ark Lab report that their agent, Memento 3, clears every level of all 25 public games in ARC-AGI-3, a benchmark of interactive puzzle games designed to test how quickly an AI can learn unfamiliar rules. It scored a mean RHAE of 100.0, using 7,518 actions against a human baseline of 17,135, or 44% of the human action count.
The striking part is how it learns. The underlying language model stays frozen, with no fine-tuning. Instead, the agent maintains a Markdown rulebook describing how each game seems to work, compiled into a Python 'world model' engine. When a prediction fails, it revises the rulebook and recompiles. A revision is kept only if it faithfully reproduces what was actually observed, a built-in check against the model fooling itself.
For comparison, the authors report that a Claude Opus 5 baseline on the same benchmark scored 40.7 mean RHAE. Ablations attribute part of the efficiency gain to the rulebook itself, and a multi-model variant cut actions on one game by a further third. A separate case study on Atari Pong reports a learned controller winning 21–0 with no language-model calls during play.
Important caveats apply. The score covers the 25 public games, not ARC-AGI-3's private evaluation set, and RHAE is capped at 100, so it can't distinguish matching human efficiency from exceeding it. All figures are author-reported in a preprint and have not been independently reproduced, and reported publication dates vary (October 8–9).
The broader idea matters beyond benchmarks: agents that learn by writing down and testing explicit rules, rather than by retraining, are cheaper to improve, easier to inspect and easier to correct. For businesses, that points to agents whose learned 'playbooks' can be read, audited and edited by people.
Why it mattersLearning through readable, testable rulebooks instead of retraining could make AI agents cheaper to improve and far easier for humans to audit.
👀 What to watch
Results on ARC-AGI-3's private set, independent reproductions, and whether 'rulebook learning' shows up in commercial agent products.
3 opportunities from this story
Auditable playbook agents for operations
Build agents for repetitive business processes (invoicing, onboarding, compliance checks) that keep a human-readable rulebook of how the process works and update it from mistakes, so managers can read and approve changes.
- Best for
- AI builders and operations consultants
- First step this week
- Prototype a rulebook agent for one back-office process and show the rulebook evolving over 20 runs.
Open the full playbook
Launch steps
- Choose one repetitive process
- Write the initial rulebook with the client
- Let the agent propose rule changes for approval
- Track error rates over time
Tools
Risks
Research results don't transfer automatically. Prove value on narrow, well-defined tasks first.
Benchmark explainers for non-experts
ARC-AGI-3, RHAE and frozen-model learning mean nothing to most decision-makers. Create clear explainers on what AI benchmarks do and don't prove, and sell briefings to companies choosing AI vendors.
- Best for
- Tech writers, analysts and educators
- First step this week
- Write a one-page guide titled 'How to read an AI benchmark claim'.
Open the full playbook
Launch steps
- Build a reusable benchmark checklist
- Explain a new result each week
- Grow a newsletter
- Offer vendor-evaluation briefings
Tools
Risks
Credibility is everything. Always note caveats and independent verification.
Game-testing and QA agents
Agents that learn game rules from interaction are a natural fit for automated game testing: exploring levels, finding softlocks and checking rule consistency. Offer AI-assisted QA to indie studios.
- Best for
- Game developers and QA freelancers
- First step this week
- Run an exploration agent on an open-source game and report the bugs it finds.
Open the full playbook
Launch steps
- Pick a simple game engine to integrate
- Build an exploration loop with logging
- Turn findings into bug reports
- Pilot with one indie studio
Tools
Risks
Studios worry about cost and accuracy. Start with narrow, measurable checks.
Get these as a PDF every 3 days
Free. One email every 3 days. Unsubscribe any time.