Lexicon · The business of it

Regulatory capture

Plain English. Regulatory capture is when the people being regulated end up writing the rules, so that "safety" law protects the incumbents' position as much as the public. In AI it is the charge levelled at the pacing proposal: a few frontier labs ask for an antitrust waiver to coordinate, a threshold that binds "frontier companies", and a crackdown on distillation, and each of those, whatever its safety merit, also raises the drawbridge behind the companies proposing it.

Why it moves money. A rule only the largest labs can comply with is a moat that capital did not have to buy. Pre-release testing, embedded evaluators and incident reporting are cheap for a company on a US$65bn run-rate and expensive for an open-weights lab; a distillation ban protects closed pricing against the four-month open lag. The counter-case is real: Hinton argues a pause "may decrease the value" of the lab asking for it, so a sincere warning and a convenient cure can both be true.

What to watch. Whether any standards body the labs form admits a non-lab member with model access; whether "frontier company" gets a defined threshold; and whether the measure that survives the midterms is the one every camp accepts (incident reporting) or the one only incumbents wanted (the waiver).

From the signals. Cohere's Gomez calls the pacing plan "a cartel by any other name". Bartholomeusz reads the pacing call as capital exhaustion. Khan: no AI exemption from existing law.

← All terms