6 Comments
User's avatar
Weekly Sovereign AI News's avatar

Very useful glossary. The point that putting a system into service covers your own use is one many organisations miss: an internal AI tool can make you a provider without selling anything. Bookmarking this for the next call where someone uses "high-risk" as if it were a defined term.

Weekly Sovereign AI News's avatar

Exactly, but if you look at most orgs already struggling with shadowai, this will become a whole new challenge

Silvia Stepitova's avatar

Exactly. It's funny with internal builds because they often make you both provider and deployer at the same time and you end up with two sets of obligations.

Marius Laurusevicius's avatar

The absence of a definition here is inherited rather than accidental. EU product law has long classified by listed category instead of by a defined risk term: Regulation (EU) 2023/1230 on machinery names no high-risk machinery either, and instead sets out Annex I Part A categories for which Article 25(3) requires EU type-examination, conformity based on full quality assurance, or unit verification. My view is that the glossary framing understates the cost of that design. A term nobody can define in the abstract still has to be settled contract by contract between provider and deployer, and that negotiation is where the ambiguity is actually paid for.

Silvia Stepitova's avatar

Classifying by listed category instead of a defined term is familiar from product law, sure. But the classification isn't decided between provider and deployer. Annex III settles it, and it stays settled whether or not anyone writes it into the contract. What putting it into contract helps with is to be aware of the obligation upfront and to cooperate to meet the obligations on both sides.

Marius Laurusevicius's avatar

Agreed, and product law has a longer record of this than people expect. The Commission's Blue Guide on the implementation of EU product rules, 2022/C 247/01, published 29 June 2022, is the standing guidance on how those rules assign roles, and the 2022 revision was extended to cover software updates and substantial modifications precisely because a role follows from what an operator does, not from what a contract calls it. My view is that contracts earn their keep on the information flow rather than the label: who tells whom, by when, and with what evidence. That part is genuinely negotiable.