This bonus episode covers the abrupt shutdown of Claude Fable 5 (alongside Mythos 5), Anthropic's most powerful model, which lasted only three days before the U.S. government forced it offline. Host Andrew is joined by Thomas Moen from Norway, and the two unpack what happened, why it matters, and what D2C operators and agencies should do about it. The framing is blunt: if you wired anything into Fable 5 during its brief window, this episode is your fire drill.
The hosts walk through the timeline. On June 12 at 5:21 PM Eastern, Anthropic received an export control directive from the U.S. government ordering it to suspend access to Fable 5 and Mythos 5 for any foreign national inside or outside the country, including Anthropic's own foreign-national employees. Because the company could not cleanly segment access by nationality, the practical result was a full shutoff for every customer. The stated trigger was a national security concern around a jailbreak that let the model read a codebase and spot software flaws. The hosts stress that no one was hacked and no data was breached. Anthropic complied but publicly disagreed, calling it a misunderstanding, and the situation was likened to a car part being recalled mid-deployment.
From there the conversation turns critical (without getting too political). Andrew, who previously worked as a press secretary in Congress, argues that government simply moves too slowly to regulate AI at its current pace, and that pulling a single model is more PR theater than a real solution. Thomas notes the chilling effect: people he knows are now experimenting with DeepSeek and looking harder at European model options, newly aware of how unstable reliance on U.S. models can feel. They also flag the irony that Anthropic's own transparency, admitting no model is perfectly jailbreak-proof, may have handed regulators their rationale. Both agree this sets a dangerous precedent: a government can now take down a frontier model after launch.
The back half is tactical. The core lesson is that single-model dependency is now a real operational risk, on par with relying on one 3PL or one ad platform. Agencies feel it harder than brands because of scale, with one analogy of 70 clients meaning 70 fires to put out. The hosts recommend auditing all AI dependencies (prompts, workflows, MCP configs, Zaps), assigning an internal owner for AI governance, building and actually testing a fallback ladder so models are not hard-coded, keeping a manual or "caveman mode" playbook, maintaining a locked manual database in parallel with AI-driven ones, and understanding the underlying logic of your skills and SOPs rather than trusting bloated AI-written ones. Thomas advocates for open-source systems and local models as insurance. The closing takeaway is that AI is shifting from a playground into pseudo-regulated infrastructure, so contingency planning is no longer optional. To connect with Andrew Foxwell reach him here [email protected]
To connect with Will Sartorious DM him here https://x.com/will_sartorius
To Connect mith Thomas Moen DM him here https://x.com/thomasmoen
To learn more about Foxwell Founders and conversations like this one, go here: www.foxwellfounders.com
