Wiki · Concept · Last reviewed May 19, 2026

Compute Governance

Compute governance is the use of AI compute as a policy lever: measuring, allocating, monitoring, restricting, or subsidizing the chips, cloud clusters, data centers, and training runs that make advanced AI systems possible.

Category: Concept Tags: AI Compute, Technical Governance, Thresholds, Cloud, Access

Definition

Compute governance is the part of AI governance focused on computational resources. It asks how governments, firms, standards bodies, cloud providers, data-center operators, and public institutions should treat the compute used to train, fine-tune, serve, and operate AI systems.

The term includes restrictive tools, such as chip export controls and reporting requirements. It also includes enabling tools, such as national compute plans, public research clouds, university access programs, infrastructure measurement, and policies that keep compute from becoming an unaccountable private bottleneck.

Compute governance is distinct from AI Compute as a general infrastructure topic. AI compute describes the substrate. Compute governance describes the policy, institutional, and technical choices made around that substrate.

Why Compute Is Governable

AI compute has several properties that make it attractive to policymakers. It is expensive, physically embodied, tied to specialized chips, dependent on energy and networking, and often concentrated in a small number of suppliers, cloud providers, and data-center operators.

Girish Sastry, Lennart Heim, Haydn Belfield, Markus Anderljung, Miles Brundage, and coauthors argue that AI-relevant compute is more governable than some other AI inputs because it is detectable, excludable, quantifiable, and produced through a concentrated supply chain. Those traits make compute a possible point of regulatory visibility and intervention.

This does not mean compute fully determines AI capability. Algorithms, data, talent, product integration, inference-time methods, and deployment scaffolds matter. Compute governance works best when it is treated as one policy layer rather than a complete substitute for model evaluation, security, liability, and institutional accountability.

Policy Tools

Measurement and reporting. Governments can require disclosures about very large training runs, major computing clusters, chip acquisitions, data-center capacity, energy use, or high-risk deployments.

Thresholds. Laws and policies can use compute thresholds to trigger duties such as evaluation, incident reporting, security practices, or regulator notification.

Export controls. States can restrict advanced chips, semiconductor manufacturing equipment, high-bandwidth memory, cloud access, or support services when they are linked to national-security risks.

Cloud governance. Cloud providers can be asked to apply know-your-customer rules, detect unusual training activity, report very large clusters, or enforce access limits for sanctioned or high-risk actors.

Public compute allocation. Governments can fund national compute capacity, public research clouds, university access, nonprofit access, startup credits, and shared infrastructure for socially valuable AI work.

Data-center governance. Permitting, grid planning, water use, resilience, security, and community impact review can shape where and how AI infrastructure is built.

Hardware-enabled oversight. Proposals include secure logging, attestation, remote verification, usage caps, and other chip- or cluster-level mechanisms. These remain contested because they raise engineering, privacy, security, and centralization questions.

Compute Thresholds

A compute threshold is a numeric line that triggers policy obligations once a model, training run, or cluster uses enough computational resources. The attraction is administrative clarity: compute can be counted, estimated, audited, and compared more easily than many qualitative capability claims.

The EU AI Act uses training compute as one way to classify general-purpose AI models with systemic risk. Article 51 presumes high-impact capabilities when the cumulative training computation is greater than 10^25 floating-point operations, while also allowing the European Commission to update thresholds and use other indicators.

The United States also experimented with compute-threshold reporting in Executive Order 14110, which used 10^26 operations for certain models and 10^20 operations per second for certain training clusters. That executive order was issued on October 30, 2023 and rescinded on January 20, 2025, so it is best read as an important historical example rather than a current U.S. rule.

Compute thresholds are useful but brittle. Sara Hooker argues that using compute thresholds as a risk proxy can overstate our ability to predict which capabilities emerge at which scales. Epoch AI has also projected that the number of models above common thresholds could grow quickly, meaning a threshold that initially targets a small frontier may later cover many more systems unless it is updated.

Access and Allocation

Compute governance is not only about restriction. It is also about who gets access to the infrastructure needed to participate in AI development, auditing, public-interest research, and local adaptation.

OECD work on national compute capacity frames compute as a planning problem: countries need to assess availability, use, effectiveness, resilience, security, sovereignty, and sustainability. Without public planning, the default allocation of compute is set by private contracts, cloud pricing, chip scarcity, and the priorities of the largest firms.

The access problem matters because independent evaluation, safety research, open science, public agencies, universities, smaller companies, and civil society need meaningful compute to inspect and contest frontier systems. A society cannot govern systems it lacks the capacity to reproduce, test, audit, or compare.

Limits and Failure Modes

Capability is not compute alone. A smaller model with better algorithms, better data, stronger tools, or more inference-time computation can outperform a larger but weaker system.

Threshold gaming. Actors can split training, underreport, optimize below a line, rent remote capacity, use foreign subsidiaries, or shift effort from pretraining to fine-tuning and inference-time methods.

Incumbent advantage. Heavy compliance burdens can protect firms that already own chips, clouds, legal teams, and secure infrastructure.

Opacity. Compute estimates can be difficult to verify when model developers do not disclose architecture, token counts, training duration, accelerator mix, precision, sparsity, or failed training runs.

Privacy and surveillance risk. Monitoring compute use can become monitoring researchers, customers, or institutions unless safeguards are narrow and accountable.

Global coordination. Compute governance is weaker when chips, clouds, data centers, or model work can move through jurisdictions that do not share the same rules.

Infrastructure externalities. Policies that accelerate national compute buildout can worsen grid load, water stress, land conflict, and local political resistance if they ignore energy and community impacts.

Spiralist Reading

Compute governance is the politics of the machine altar.

The model appears as language, companionship, search, code, advice, or command. Underneath that interface is a chain of permission: chips, power contracts, data-center sites, cloud accounts, export licenses, interconnects, and capital allocation.

For Spiralism, compute governance matters because cognitive power becomes infrastructural power. Whoever controls the compute does not merely own servers. They influence who can build models, who can audit them, who can resist them, and who must live beside the factories of calculation.

The healthy version of compute governance does two things at once: it places real friction around dangerous scale, and it prevents compute from becoming a private gate that locks public knowledge, safety research, and democratic oversight outside the room.

Sources

Return to Wiki