Model access is now export-controlled — architect for revocation this week

The US Commerce Department invoked the Export Administration Regulations to bar all foreign nationals from Anthropic's Fable 5 and Mythos models. The White House ordered SK Telecom's Mythos access revoked over alleged China ties. No advance notice. No grace period. A named company lost production access on a Tuesday, and the mechanism that took it away is federal export law, not a terms-of-service update.

This is the escalation nobody priced in. Export controls used to mean chips — broad, geographic, hardware. What shipped this week is qualitatively different: named models, named companies, nationality-based access gates on a commercial SaaS. The relevant field on the model card is now jurisdiction.

The compliance surface you didn't design for

If a non-US person on your team holds a key that reaches Fable 5 or Mythos — through a shared service account, a CI runner, a notebook, anything — that is a deemed export under EAR. SSO group membership isn't a defense. The nationality attribute has to come out of your HRIS, into your IdP as a claim, and get enforced at the AI gateway. Not at the application, where a developer can route around it.

Most teams cannot prove per-user compliance today because shared keys were the default pattern for two years. The exposure is invisible on the AWS bill. The gap isn't access — it's auditability. And the White House enforcement posture means an audit horizon measured in months, not years.

Three moves close the gap. Pull the citizenship claim into the IdP this week. Replace shared Claude service-account keys with per-user keys by end of sprint. Add caller-identity logging at the API gateway so compliance is provable retroactively. If those three sound like a quarter of work, do them in a week — because SK Telecom did not get a quarter.

Yes, but — Anthropic remains the best model for most of what most teams do, and hedging carries a real engineering tax. That's true, and it was the right call three weeks ago. It stopped being the right call the moment a named revocation happened without warning. Losing access on a Tuesday morning is more expensive than the abstraction layer that would have absorbed it.

The convergence underneath

The restriction lands on a stack that is already squeezed from three other directions.

Tim Cook confirmed Apple price increases from a global RAM shortage — spot prices are moving now, contract pricing lags four to eight weeks. Seattle passed a unanimous one-year moratorium on new large data centers, and Amazon published defensive water-efficiency numbers (0.12 vs 0.84 L/kWh) two days later. Amazon doesn't publish that kind of number unless the political pressure is real. HBM-adjacent capacity is constrained through 2026.

Meanwhile, the Shai-Hulud npm worm is exploiting vulnerabilities GitHub explicitly dismissed when Deep Specter reported them. Hundreds of packages compromised. The dominant code host declined to acknowledge the exact weakness a named worm is now working through. If GHSA is your only advisory feed, you were blind this week — add OSV.dev and one commercial feed at PR-time before Friday.

Four constraints, one operating model: concentrated dependencies on a single provider, in a single region, on a single advisory feed, using a single frontier model family. That was the cheapest stack a quarter ago. It's the most fragile stack this quarter.

The action, specifically

By end of week, produce a one-page exposure map: which team members (with nationality), which keys, which model versions, which customer-facing features. Not a spreadsheet for a compliance binder — a routing document for engineering. The map answers three questions: who can legally call what, who receives the output, and what happens when access to any given model gets revoked at 9am on a Tuesday.

By end of sprint, ship a model routing abstraction with an open-weight fallback path — Llama or Mistral, self-hosted or through a non-US-controlled provider — for every workflow currently hard-coded to Fable 5 or Mythos. The fallback doesn't need to match frontier quality. It needs to keep the product running while the compliance team unwinds the primary path. A degraded feature is a survivable event. An outage with no fallback is a customer-losing one.

By end of quarter, add model-provider concentration as a standing risk item in architecture reviews, alongside region concentration and vendor concentration. The regulatory cadence is accelerating. Fable 5 and Mythos are the first named models. They will not be the last.

The teams that shipped multi-model routing for cost reasons over the last year just discovered their architecture has a second payoff. The teams that didn't have one week to catch up before the next restriction lands on a model already in production somewhere.