Your model is an upstream dependency you don't control. Plan accordingly.

Fable 5 and Mythos 5 went dark this week. Not a soft sunset with a six-month migration window. A US export directive, and within hours the models were unavailable to any foreign national anywhere on earth. Enterprise teams outside the US woke up to API calls failing against a model they'd shipped to production (VentureBeat). The trigger was a jailbreak posted to X around June 10 by Pliny the Liberator, which Anthropic disputes is even a real jailbreak (TechRadar). Doesn't matter for your code. The model is gone while Anthropic and the government negotiate whether it comes back under modified safeguards.

Here's what I keep turning over. Every dependency we manage has a failure model. npm packages get yanked, APIs deprecate, certs expire. We built tooling for all of it: lockfiles, version pins, fallback DNS. But model availability failing for political reasons, with zero notice and no technical signal you could have monitored? That's a failure mode most stacks never designed for. The teams that hardcoded a single frontier model ID broke. The teams that abstracted the model behind a router degraded gracefully (ChatForest).

So do this today, not next sprint. Put a router in front of your model calls if you haven't. Re-pin Claude Code and your API integrations to Opus 4.8 and confirm auto-mode's fallback actually resolves to an available Opus model. Grep your CI and scripts for hardcoded model IDs and make sure they fail open to a working model, not closed to a 404 (TokenMix). Treat "is my primary model still reachable" as a monitored health check, same as you'd watch any upstream.

The deeper move, and this connects straight to story five, is that geopolitical revocability is now a real argument for self-hosted open weights. A model running on weights you downloaded can't be recalled by directive. I'm not saying rip out your frontier API. The quality gap is real. But the calculus for keeping a tested open-weights fallback in the chain just changed from "nice resilience exercise" to "the thing that kept me shipping last Tuesday." European commentators are already calling this the end of the "safe American cloud" assumption, and the digital-sovereignty crowd got the best week of evidence they've had in years (VentureBeat). Don't hardcode a single model ID. That's the whole lesson.