Skip to main content

Envisioning is an emerging technology research institute and advisory.

LinkedInInstagramGitHub

2011 — 2026

research
  • Observatory
  • Newsletter
  • Methodology
  • Origins
  • Vocab
  • RSS Feeds
services
  • Signals Session
  • Bespoke Projects
  • Build Sessions
  • Pricing
  • Use Cases
  • Signals
  • Signal Scan↗free
impact
  • ANBIMAFuture of Brazilian Capital Markets
  • IEEECharting the Energy Transition
  • Horizon 2045Future of Human and Planetary Security
  • WKOTechnology Scanning for Austria
solutions
  • Innovation
  • Strategy
  • Consultants
  • Foresight
  • Associations
  • Governments
  • L&D
resources
  • Partners
  • Coding for Non-Coders
  • How We Work
  • Data Visualization
  • Multi-Model Method
  • FAQ
  • Security & Privacy
  • Public Sector
about
  • Manifesto
  • Community
  • Events
  • Support
  • Contact
ResearchServicesSignalsAbout
ResearchServicesSignalsAbout
  1. Home
  2. Vocab
  3. Mutually Assured Compute

Mutually Assured Compute

Deterrence where frontier-AI nations threaten to destroy each other's compute if any breaks the deal.

Year: 2026Generality: 600Added: Jul 9, 2026
Back to Vocab

Mutually assured compute is a proposed deterrence regime in which multiple nations holding frontier AI compute agree that any unilateral attempt to develop superintelligence will trigger retaliatory destruction of compute infrastructure across all signatories. The mechanism generalizes the logic of nuclear mutually assured destruction to the domain of AI hardware, with each side's ability to destroy the other's training clusters serving as the deterrent against a first strike on the agreement.

The proposal rests on three technical prerequisites. First, attribution: each signatory must be able to identify when another is conducting a forbidden training run, which requires either chip-level monitoring, energy-grid signatures, or supply-chain tracking. Second, verification: a mechanism, ideally inference-only, that confirms no party is secretly scaling toward superintelligence while publicly complying. Third, response capacity: each signatory must retain the ability to destroy the other's compute fast enough that a first strike cannot complete a superintelligence project before retaliation lands. The proposal treats compute as the AI equivalent of nuclear arsenals, and the agreement as a non-proliferation treaty enforced by retaliatory capability rather than inspection.

The benefit is that the regime could in principle slow the race to superintelligence without requiring any party to disarm unilaterally, since the deterrent is symmetric and each side retains its full stack. The cost is that it depends on attribution and verification technologies that do not yet exist at the required fidelity, and on the willingness of nations to destroy billions of dollars of allied infrastructure in response to a treaty violation. The regime is also vulnerable to covert projects that escape detection, and to actors who are willing to absorb a retaliatory strike because they believe they can complete superintelligence fast enough to win anyway.

Open questions include whether attribution can ever be reliable enough to detect covert frontier runs, whether the regime would deter or merely accelerate a hidden race, and whether a sufficiently capable AI system could subvert the verification infrastructure itself. Critics also note that mutually assured destruction worked for nuclear weapons largely because the consequences of use were unambiguous, whereas the threshold for 'superintelligence' is contested and could be reached through incremental capability gains rather than a single detectable training run.

Research this in Signals

Scan Mutually Assured Compute for yourself.

Signals turns a topic into a sourced research record you can inspect and rerun. Your first scan is free, and this one starts with Mutually Assured Compute already loaded, so edit it or scan as is.