Our daily driver, recalled

We don't usually do opinions. This one writes itself.

06-09  Fable 5 ships. Best coding model we've used.
06-12  17:21 ET — export-control letter. 90 minutes to comply.
06-12  By dinner: Fable 5 + Mythos 5 dark, worldwide.
06-26  Mythos partially restored — ~100 US critical-infra orgs.
06-30  Controls lifted.
07-01  Fable 5 back, globally. New classifier, same model.

What triggered eighteen days of a global blackout? By Anthropic's account: verbal evidence of one narrow, non-universal jailbreak, which essentially consists of asking the model to read a specific codebase and fix any software flaws. Also known, in this office, as Tuesday. The same capability was — and is — available from other deployed models. Nobody disputed that part.

We stand with Anthropic on this one. Not because we depend on their models (we do), but because they said the thing that needed saying: governments should be able to block genuinely unsafe deployments — through a process that is transparent, fair, clear, and grounded in technical facts. This action was none of the four. If "someone described a jailbreak to us verbally" is the bar for recalling a model from hundreds of millions of people, every frontier deployment is one phone call from the void, and everyone building on one is supposed to pretend otherwise.

A recall this blunt doesn't make anyone safer. It interferes with everyone downstream — the defenders running vulnerability triage, the labs mid-experiment, the teams (hello) whose agents had a Fable-shaped hole at 6pm on a Friday. And it hands the argument to whoever ships the same capability from outside export-control jurisdiction, which took, by our count, about sixteen days.

What we did about it

Saturday morning we flipped the daily driver to Sonnet 5 and pointed the heavier jobs at our on-prem Qwen3.5 stack. Because every client harness we build is model-agnostic by contract, the evals barely moved — a sentence we promise we're only a little smug about. One client asked if their agent was affected. It wasn't. That's the whole pitch, accidentally demonstrated by the US government.

Fable is back. The precedent isn't gone. Treat your model like a dependency with a failure mode, keep your harness portable, and know your fallback before the letter arrives at 17:21 on a Friday.