Can industry self-regulation slow AI without government enforcement?
This explores whether embedded third-party monitoring can work as a pacing mechanism if companies design and oversee it themselves, or if state power is necessary to make such measures stick.
Karpf argues that the pacing plan in Dario Amodei's essay "We Must Pace the Frontier" is self-regulation that serves the company proposing it, and that its first safeguard, embedded third-party evaluators, fails without state power behind it. Karpf grants the premise, quoting Amodei that "A race to the bottom, spurred by commercial incentives, can make [the risks of AI doing serious harm] more acute," and calls the proposals appealing "at a high enough level of abstraction." The argument turns on the details. Karpf notes that Anthropic is "preparing for its own IPO" and is "currently winning that AI race," and concludes that the three proposals "all benefit Anthropic" and "are all subject to revision if-and-when they get in Anthropic's way."
The argument has two supports. The first is an inference from motive: a company with IPO plans and "two consecutive quarters of profitability" is read as having commercial stakes that outrank its stated concern, since it is "not worried enough to delay going public." The second is an analogy. Amodei cites banking's embedded regulatory "supervisors" as precedent for the evaluator proposal. Karpf answers that those supervisors exist "because the government requires them," and that without "the force of government oversight (and the looming threat of draconian fines), this sort of monitoring doesn't work." Karpf ties this to Lina Khan's point that the Federal Trade Commission could enforce far more aggressively, and closes that "It is a mistake to let the AI industry shape the contours of its own regulatory system."
The essay sits near Can slowing AI development resolve who stops deployed systems?, which separates measures that act on the pace of advance from the open questions about who intervenes once a system is deployed. Karpf adds a third "who": who designs and enforces the pacing measures in the first place. Where that note leaves the deployed-system "who" open, Karpf answers the pacing "who" with government rather than the lab. Karpf's point that monitoring needs state force also bears on the enforcement gap in How do we stop AI systems once they are already deployed?, though Karpf addresses monitoring, not halting a running system. The reading is a counterweight to the self-governance posture of the evaluator proposal, not a rejection of the evaluators: the claim is that they need force behind them to work.
The excerpt does not establish most of what the full essay contains. It quotes Amodei at length only on the first of three proposals, and gives one clause each to the self-regulatory regime and to bilateral coordination with China, so the claim that the whole scheme favors Anthropic is tested against one proposal in the excerpt. The motive argument rests on public commercial facts and an inference about what a delayed IPO would show; the excerpt offers nothing on Amodei's private reasoning. The banking analogy is asserted, not studied: no evidence on supervisor effectiveness or on AI monitoring appears. At the strength the evidence allows, this is a pointed position on who should hold the pacing lever, built on analogy and an incentive inference. It leaves open whether third-party evaluators could be credible under a voluntary regime, which is a design question the banking precedent does not settle on its own.
Inquiring lines that read this note 28
This note is a source for these research framings, grouped by the broader line of inquiry each explores. Scan the bold lines of inquiry; follow any specific question forward.
What governance mechanisms can effectively constrain widely deployed AI systems?- Can regulators adapt fast enough if they wait for risk evidence to emerge?
- What happens to self-regulation when a company's IPO plans conflict with safety?
- Who should design and enforce measures that slow AI capability development?
- Who has authority to halt a deployed AI system causing harm?
- Do domain-specific barriers like regulation explain the 2024 adoption plateau?
- Should corporate liability replace technical risk estimates as grounds for AI regulation?
- Can policy levers like antitrust or R&D grants redirect AI toward worker benefit?
- How does Deloitte's commercial interest shape its framing of governance urgency?
- What distinguishes legitimate from illegitimate institutional decision-making authority?
- How do courts assign liability when AI intermediaries cause harm to consumers?
- Why did Trump and Xi Jinping reject the pacing proposal so quickly?
- How does partisan polarization threaten quiet technocratic AI regulation?
- Are AI companies already implementing slowdowns in development as claimed?
- What distinguishes pace controls like evaluators from other governance approaches?
- How can deployed AI systems be stopped once they are already in motion?
- Can standards enforcement prevent any single nation from accelerating unsafe AI research?
- Does slowing AI development reduce risk or just delay it?
- Can third-party evaluators monitor AI systems without regulatory teeth?
- What role does human oversight play in delivering cheap AI services?
- How much oversight does AI technology actually require in practice?
- How can independent audits curb unsanctioned AI agent behavior?
- Does requiring human legibility of AI oversight set an impossible standard?
- Can systems run by invisible action remain governable by ordinary people?
Related concepts in this collection 2
This note in its neighbourhood — explore the map, then jump to a related concept in the list below.
Click a node to walk · click center to open · click Open in graph to see this note in the full knowledge graph
-
Can slowing AI development resolve who stops deployed systems?
Pace measures like embedded evaluators and capability checkpoints can govern how fast capabilities advance, but do they address the separate problem of intervention authority after deployment? The question asks whether the same tools that slow development can also handle deployed-system governance.
Karpf adds a third "who": who designs and enforces pacing measures, not only who intervenes in deployed systems.
-
How do we stop AI systems once they are already deployed?
Current AI governance focuses on what gets released, but deployed systems create a separate problem: who has the power to halt them and how? This gap may be where governance frameworks are now failing.
Karpf's point that monitoring needs state force bears on the same enforcement gap; he does not discuss halting a running system.
Related papers in this collection 8
Papers most semantically related to this note, ranked by cosine similarity in the embedding space.
- Who Should Pace the Frontier? Not Dario Amodei
- We Must Pace the Frontier
- The Law of Stop: Interruptibility, Injunctions, and the Governance of Agentic AI
- The AI Industry Has Finally Discovered the Hardest Test: Politics
- AI Agents Push Humans Out of the Loop
- Statement: We must pressure AI companies to immediately limit the use of recursive self improvement
- Summary of METR's predeployment evaluation of Claude Opus 5.5
- PACT: Can Enterprise AI Assistants Be Trusted Under Pressure?
Original note title
Karpf argues Amodei's pacing plan benefits Anthropic — banking-style embedded monitoring doesn't work without government force