Skip to main content

Envisioning is an emerging technology research institute and advisory.

LinkedInInstagramGitHub

2011 — 2026

research
  • Observatory
  • Newsletter
  • Methodology
  • Origins
  • Vocab
services
  • Signals Session
  • Bespoke Projects
  • Build Sessions
  • Use Cases
  • Readinessfree
  • Signals
  • Free 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
resources
  • Partners
  • Coding for Non-Coders
  • How We Work
  • Data Visualization
  • Multi-Model Method
  • FAQ
  • Security & Privacy
about
  • Manifesto
  • Community
  • Events
  • Support
  • Contact
ResearchServicesSignalsAbout
ResearchServicesSignalsAbout
  1. Home
  2. Vocab
  3. Regulatory Capture

Regulatory Capture

When a regulator ends up advancing the interests of the industry it oversees.

Year: 1971Generality: 700Added: Jun 27, 2026
Back to Vocab

In AI policy, regulatory capture describes the pattern by which the agencies, standards bodies, or rule-making processes established to oversee the AI industry instead come to advance the commercial and political interests of the largest AI labs. The mechanism is the same one documented in banking, telecommunications, energy, and pharmaceuticals: the regulated industry has structural expertise advantages, controls funding for the regulator's research and personnel, rotates staff through agency and corporate roles, and frames every technical question in ways that favor its own position. The result is rules that protect incumbents, raise compliance costs in ways only the largest players can absorb, and reframe the public-interest goal — AI safety, model accountability, compute governance — as something that requires exactly the resources and infrastructure the incumbents already have.

Mechanically, AI regulatory capture shows up in three places. First, compute thresholds: proposed rules that require capabilities evaluations, security clearances, or compute reporting at scales that only frontier labs can meet, which lock smaller open-source competitors out of the regulated zone. Second, safety standards: voluntary or mandatory safety frameworks whose definitions, methodologies, and evaluation regimes are authored by the labs themselves, then promoted to regulators as the de facto industry standard. Third, export-control and KYC regimes: user-vetting and end-use restrictions presented as national-security measures that, in practice, can only be implemented by firms with the legal and compliance apparatus of a frontier lab, and that effectively grant incumbents regulatory cover against open-source competition. In each case, the public-interest argument is genuine, but the policy shape is one the incumbents can satisfy and smaller players cannot.

The advantage of the regulatory-capture frame in AI policy is that it gives critics — open-source advocates, public-interest technologists, smaller-lab competitors — a structured way to challenge rules that look defensible in isolation but in aggregate benefit only the incumbents. The frame also surfaces useful diagnostic questions: who wrote the evaluation methodology, who funded the regulator's technical staff, who reviews the comment letters, what are the career paths between agency and the regulated firms. The cost is overuse: the term is applied to any industry-friendly outcome, which dilutes its force. Capture is also easy to claim from the outside but hard to prove without rigorous institutional evidence, and the term has been weaponized politically across the AI debate, with both sides accusing the other of engineering rules to entrench their position. A careful application requires distinguishing capture (where the industry shapes the rule) from regulatory failure (where the agency acts incompetently in the public interest), from regulatory forbearance (where the agency deliberately chooses not to enforce), and from the broader phenomenon of policy capture in legislatures.

Open questions include how to design AI regulatory institutions that are structurally resistant to capture — independent technical capacity at the agency, career-path firewalls, open comment processes, public-interest seats on standards bodies — and how to detect capture early enough to intervene before rules harden. The deeper question is whether any regulator can match the rate of change and the technical depth of frontier AI development, and whether the appropriate response is therefore to slow rule-making (so capture has less to capture) rather than to accelerate it. Historically, regulatory capture has been a slow-moving phenomenon in mature industries; in AI, where the technology and the companies mature on a timescale of months, the question of whether capture can be diagnosed and reversed in time is genuinely open. The concept itself is older than AI — George Stigler's 1971 economic theory of regulation is the canonical reference — but its application to frontier-model policy is currently the most consequential live debate in the field.

Research this in Signals

Scan Regulatory Capture 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 Regulatory Capture already loaded, so edit it or scan as is.