Unannounced upstream model change

What it is

A hosted model is not a fixed thing. Providers retrain, patch safety filters, change default settings and move traffic between versions, often under the same model name. Each change can alter how the model responds to the organisation's prompts: accuracy on a task, tone, refusals, format. The organisation tested and approved its system against the earlier behaviour. The risk is that the ground moves and nobody downstream is told. The internal counterpart is covered in uncontrolled AI change.

How it happens

• The system calls a model alias that always points to the latest version.
• The provider changes a safety filter or system-level instruction.
• A supplier's product swaps the underlying model to cut cost.
• Change notices are sent to an unread mailbox, or not sent.

Why it matters

Validation, fairness testing and approval no longer describe the system in use. Faults appear with no corresponding release, which makes them slow to diagnose. In a regulated process, an unassessed change of this kind is a control failure regardless of who made it.

Warning signs

• The model version in use is not pinned or recorded.
• Outputs shift on a date when nothing was released.
• The contract gives no right to notice of change.
• No test suite runs on a schedule against the live model.

Who owns it

The system owner is accountable for knowing what version is in use. Engineering pins versions and runs tests. Procurement secures notice rights in the contract.

In practice

A firm's complaint-classification system begins sending more cases to the wrong team. Nothing had been deployed. The provider had updated the model behind the same name three days earlier, and it now words its answers slightly differently from what the firm's parser expects. The same pattern generalises to any system built on a component its owner does not control.