AI Pacing Is So Yesterday: We Need to Treat AI as Critical U.S. Infrastructure
Failed to add items
Add to basket failed.
Add to wishlist failed.
Remove from wishlist failed.
Adding to library failed
Follow podcast failed
Unfollow podcast failed
-
Narrated by:
-
By:
When Dario Amodei published his essay calling on frontier labs to pace their releases, the leaders of the largest competing labs endorsed it within a weekend, and Microsoft followed on Monday.
In this episode, Ray Rike and Peter Buchanan examine what "pacing" actually means, why each lab defines it differently, and why self-governance by frontier labs leaves enterprises, governments, and emerging AI players without a seat at the table. They then make the case for formally designating frontier AI as part of U.S. critical infrastructure, with government-hired evaluators funded by lab fees.
Key topics covered:
- Anthropic's three-step pacing plan, including outside evaluators with employee-level access and a commitment of up to $1 billion over five years for Accenture to serve as an independent evaluator
- How the Anthropic (FAA model), Google DeepMind (FINRA model), and OpenAI (IAEA model) approaches differ, and why Cohere's Aidan Gomez compared the arrangement to the bond rating agency cartel that preceded the 2008 financial crisis
- CrowdStrike threat data showing 88% of observed exploits landed within 48 hours of disclosure, with AI agent activity generating 2.5x the event volume of human activity
- Why the government is under-resourced to respond: NIST's AI standards center runs on a $15 million budget against an estimated $84 million need, and CISA headcount has fallen from roughly 3,400 to about 2,300
- How the existing 16-sector critical infrastructure framework works, and a proposed tiered oversight model where only the most powerful frontier models carry the heaviest requirements
- What enterprise executives should do now: plan for exploit windows measured in hours, monitor agent activity separately from human activity, protect model weights, and build 72-hour incident reporting capability before regulation requires it
Subscribe to the AI to ROI podcast, leave a five-star rating, and let us know which stories, topics, and guests you would like us to cover next.
Read the full September 22nd edition at ai2roi.substack.com
See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.