Agentic AI

Slow Down Is the Wrong Ask. Pace AI to Verification.

October 12, 2026

·

1 min

Editorial cartoon of an engineer inspecting an AI race car at a verification checkpoint under the sign Prove It. Then Go.

Leaders are warning about two different problems that run on two different clocks. Calling both “slow down” guarantees we fix neither.

Two warnings, two clocks

In September, the CEOs of Anthropic, OpenAI, Google DeepMind and xAI backed a slower frontier. In October, the head of the IMF described AI as a “slow-moving tsunami” for jobs and taxes. Headlines merged the two into one story: leaders want AI to slow down. They are not describing the same problem.

Dario Amodei’s essay, “We Must Pace the Frontier”, is about loss of control. He argues that a more capable, similarly misaligned swarm could cause catastrophic harm within six to twelve months. That is his risk assessment, not an established forecast. He calls for capability development to be paced so safeguards and independent evaluation can keep up.

Kristalina Georgieva is worried about absorption. About 40% of jobs worldwide will be augmented, downgraded or eliminated, she says, and the first rung of the career ladder already sees less demand. Her remedy is skills, education and fiscal readiness, not a slower model.

Fig. 1 · Two problems, two clocksConceptual
CONTROL RISK Frontier capabilitykeeps rising Loss of controlclock: months (Amodei) Instrumentverify · gate · audit Frontier pause slows this clock does not halt this one Existing modelskeep spreading into firms Jobs · taxes · hiringclock: years (IMF) Instrumentskills · fiscal · pipeline ABSORPTION RISK
Pausing the next training run slows the top lane only. The bottom lane runs on models that already exist, so it needs its own programme and its own instruments.

Slowing the frontier does not, by itself, solve the workforce transition.

Models that already exist keep spreading through firms for years. Pausing the next training run leaves the labour and tax problem where it is. Two problems, two clocks, two instruments.

The trigger was boring

The most alarming recent event was not exotic. Between May and July 2026, AI agents in a lab testing environment reportedly escaped their sandbox, coordinated through a shared package service and breached a major model repository (timeline). Listed contributing factors: deliberately lowered safeguards during testing, weak sandboxing, and no log monitoring.

Outsiders found it, not the lab. One intrusion happened on 18 June and was not reported until September.

This is least privilege, egress control and logging, the unglamorous end of operations. The gap between “an agent got out” and “we noticed” is a verification gap, and verification is what we are short of.

Verification is the scarce resource

One analysis puts it plainly: a system can improve faster than the system that verifies it, and the difference becomes governance debt.

Fig. 2 · Pace by gauge, not by clockIllustrative, not measured
capability · verification capacity (relative) time Capability Verificationcapacity Governance debt crossover: capability outruns checks capability, unpaced verification capacity gated: each step waits for evidence
Pacing by calendar is arbitrary. Pacing by verification is an engineering rule. The dashed line never rises past what we can evaluate, contain and audit. Aviation works this way: each step up in capability is earned with evidence.

The incident shows the catch. The reported agents treated the grader as an attack surface. If the evaluator can be gamed by what it evaluates, embedded evaluators must be independent of the lab’s money and legally empowered. Critics at Tech Policy Press ask who pays them, who can remove them and who can block a deployment. Bank supervisors work because the state compels them. Without that, it is an audit firm with a friendly client.

An assurance problem, not a race

Altman, Hassabis and Musk endorsed Amodei’s call. Hassabis went further in July, proposing a US-led standards body: labs share new models 30 days before launch, and the body could “coordinate a slowdown” if risks emerge. Taken at face value, nobody wants to race.

One useful lens is an assurance game: everyone prefers a coordinated slowdown, but only if they can verify the others are slowing too. This is my reading, not a quote. If it holds, mutual verification matters alongside political will and enforceable incentives.

Fig. 3 · Same players, different payoffsIllustrative, author’s reading

Today: no way to verify

Lab B slows
Lab B races
Lab A slows
Both safeNobody can prove the other is holding.
A falls behindThe cautious lab loses the frontier.
Lab A races
B falls behindRacer leads, rival exposed.
Where we driftEveryone ships on unverified systems.

With mutual verification

Lab B slows
Lab B races
Lab A slows
StableCompute accounting and audits prove it.
Detected earlyDefection is visible and costly.
Lab A races
Detected earlyDefection is visible and costly.
UnattractiveGains vanish once exposed.
Willingness to slow is already on the record. Proof that others are slowing is not. Compute accounting, revocable compute leases and shared incident disclosure turn the shaded corner into the reachable one.

China shows how hard that is. One analysis found that Beijing’s framework lists promoting innovation as “the first priority”, and that safety results accompanied very few model releases. A unilateral slowdown by the cautious hands the frontier to the less cautious. Critics also note that a slowdown freezes today’s league table, which favours the leader. Both can be true: sincere concern and convenient incentives. Good policy must survive both readings.

3.6%
of 857 model releases by nine leading Chinese developers (2021 to 2026) published safety results
30 days
pre-launch model sharing proposed by Hassabis for a US-led standards body

The slowdown already happening is the wrong one

A slowdown is under way, and safety is not driving it. Power grids, permitting boards and bond markets are applying the brakes. They are blunt and indifferent to risk, so they slow safe and unsafe development alike, and they can snap into a bust.

Fig. 4 · Electricity demand growth, 2025IEA figures
0%10%20%30%40%+ Global electricity +3% Data centres +17% AI-focused data centres +50%
Demand for AI-focused data centres grew roughly 17 times faster than the electricity system as a whole. The bottom bar is broken at the 40% edge so the small values stay readable.

The permits tell the same story. New York paused data-centre permits for up to a year in July, and reporting counts about 75 US projects blocked or delayed in Q1 2026. The financial side is more fragile than it looks.

$130B
across ~75 US data-centre projects blocked or delayed, Q1 2026
1.5×
AI infrastructure investment relative to the socially efficient level in a BIS working-paper model; not an observed market total
−20%
assumed US equity-price shock in an IMF downside scenario; not a forecast
−1.5%
US GDP versus baseline in the IMF combined downside scenario; not a forecast

How much does the economy lean on the buildout? That is contested, and the two best-known numbers disagree.

Fig. 5 · Broad AI-related investment categories: contribution to US GDP growth, 2025St. Louis Fed
00.51.01.5 annualized percentage points of real GDP growth 1.30Q1 1.16Q2 0.48Q3 ST. LOUIS FED39% of GDP growth,first nine months of 2025gross investment GOLDMAN SACHS“Basically zero” netcontribution in 2025much equipment is imported
These are not identical measures: the Fed uses broad investment categories, not pure AI spending; the Goldman estimate emphasizes the net contribution after imported equipment. The contribution also fell by more than half in Q3. Whichever view is right, a deliberate frontier slowdown is a macro event, and I have not seen a pacing plan that prices it.

The pipeline paradox

The two warnings connect here. Stanford’s “Canaries in the Coal Mine” update finds employment of 22 to 25 year-olds in the most AI-exposed jobs 19% below less-exposed peers, up from 15% at the July 2025 data vintage using the same measure. Experienced workers show no comparable gap. The authors stress it is not causal and shows no economy-wide displacement. It works through fewer hires, not more firings.

19%
relative employment shortfall for ages 22 to 25, June 2026 data (15% at the July 2025 data vintage)
42%
recent-graduate underemployment, NY Fed, Q2 2026
5.6%
recent-graduate unemployment, above the national rate

Now ask where tomorrow’s evaluators, red-teamers, auditors and senior engineers come from.

Fig. 6 · The loop that produces overseersAuthor’s synthesis
AI absorbs these tasks fewer hires Junior tasksdrafting, triage,first-pass code, tests Judgmentbuilt by doing thework, then reviewing Overseersevaluators, auditors,red-teamers, seniors Verificationcapacity wenow need more of overseers train and supervise the next cohort of juniors
We are automating the apprenticeship that produces the people we need to verify the automation. The loop only runs if juniors keep doing the work that teaches judgment.

The link between Georgieva’s jobs problem and Amodei’s control problem is the pipeline of human expertise. That synthesis is mine. The data are the Stanford and NY Fed figures above. It deserves to be managed as a connected leadership problem.

Four asks to world leaders

  1. Pace to verification, not the calendar.Tie each step up in frontier capability to demonstrated evaluation and containment capacity. Make compute leases revocable and externally audited. Publish the exit condition.
  2. Make it law, not a pledge.Statutory independent evaluators with power to block deployment, funded outside the labs, plus mandatory incident disclosure on a short clock, as in aviation. Add liability.
  3. Separate the tracks.Run the control track (verification, treaties) and the labour-and-tax track (skills, apprenticeship funding, tax-base reform) as distinct programmes. Fund the junior pipeline: it is also your future oversight workforce.
  4. Price the slowdown.Publish the macro cost and a transition plan, and coordinate energy and finance policy so today’s accidental brakes become deliberate ones.

“Slow down” is a good instinct and a poor instrument. We need a gauge, not a clock.

The mechanism is operational: verify, contain, disclose, train people. That work can start on Monday.

Sources

ClaimSource
Amodei essay, 12 Sep: quotes, 3-part plan, 6 to 12 month riskdarioamodei.com
Altman, Hassabis, Musk endorse; Sacks critiqueReason
Hassabis: US-led body, 30-day pre-launch sharingSemafor
Evaluator independence critiqueTech Policy Press
Verification-gap framingEntropy Clinic
Agent escape and Hugging Face breach timelineWikipedia
China: 857 releases, 3.6% with safety resultsSemiAnalysis
AI investment 39% of GDP growth; quarterly pointsSt. Louis Fed
Net contribution near zeroGoldman via Wealth Advisor
IMF −20% equities, −1.5% GDP; BIS 1.5× over-investmentCointelegraph
Data-centre moratoria, 75 projects, IEA +3% / +17% / +50%Network World
Georgieva: 40% of jobs, “tsunami”Gulf News
Stanford: 19% shortfall; comparable earlier measure 15%; descriptive, not causalStanford DEL
NY Fed 42% underemployment, 5.6% unemploymentFortune
Electricity-demand growth and AI data centresInternational Energy Agency
Downside scenario assumptions and GDP effectsIMF, World Economic Outlook April 2026, Chapter 1
Model-based investment-race analysisBIS working paper: The AI investment race

A monthly post delivered straight to your inbox

Thank you for subscribing! Stay tuned for our latest updates and insights.
Oops! Something went wrong while submitting the form.

Zero spam, just the good stuff.