Vendor quality gate

For most agencies the deepest governance decision is made at purchase, when leverage is highest and attention lowest. A vendor gate makes procurement carry the governance load: access to model behavior for independent evaluation, documentation of training data provenance, notification and re-approval on model updates, data rights that survive contract end, and exit terms that make discontinuation feasible. Where a use falls in a regulated high-risk tier, some of that load is already set by statute rather than by the buyer: conformity assessment before the tool is placed on the market, monitoring after it is, and human-oversight measures documented throughout. The gate is then a way of holding a supplier to obligations that exist whether or not the contract mentions them.

The Atlas shows the price of its absence: opaque systems the deploying institution could neither inspect nor explain, defended in court by agencies that did not build them and could not audit them.

The update clause deserves emphasis. A vendor's silent model update is a redeployment without review — the gate must catch version N+1, not just version 1.

The data clause deserves equal weight. Running client data through a model hosted by a vendor with no data-processing agreement — and no option to self-host — is an unguarded path out of the system: the vendor decides what happens to the data, and a silent update can re-route it. A signed data-processing agreement (or self-hosting the model) closes that path; procurement is where the leverage to demand it exists.