liveBook · Manning

Substantial modification

As explained in AI Governance

A substantial modification is a change to an AI system that affects its compliance or changes its intended purpose in a way not foreseen by the original provider.

A substantial modification changes an AI system’s compliance or intended purpose in a way its original provider did not foresee. The modifier may become the provider of the changed system. section 7.3.2

From recommendations to automatic approvals

A bank uses a credit-scoring tool designed to support decisions reviewed by credit officers. If its engineers add a browser extension that automatically approves applications above a threshold, they have changed the system’s operation beyond what the vendor validated; the bank becomes the provider of the modified system. section 7.3.2

Assess changes against the original provider’s intended purpose and assessment:

  • Changes to capabilities, data sources, deployment context, or upstream models may require reassessment when they go beyond what the original assessment covered. section 7.5.1
  • Heavy fine-tuning of another provider’s deployed high-risk system can amount to substantial modification; fine-tuning alone does not automatically make someone a provider. section 7.3.6
  • Document expected changes in the initial conformity assessment. Changes within that documented envelope do not count as substantial modifications. section 7.5.1
Figure 7.13 Classification and role decision tree. The tree produces two outputs: a risk classification and a role assignment. Together, they determine which obligation set applies and which evidence pack you need.

Use the decision tree to consider how a change affects risk classification and role assignment, which together determine applicable obligations. section 7.3.6

How AI Governance covers it

How deep it goes
Defines the concept and illustrates it with system changes, but gives no universal quantitative threshold for substantial modification.
Examples
Uses automated credit approvals, high-risk-system fine-tuning, and changes to capabilities, data sources, or deployment context.
What it assumes
Assumes familiarity with provider and deployer roles, intended purpose, and conformity assessment.
What you can do after
Evaluate whether a system change may transfer provider responsibility and whether planned changes fit a documented assessment envelope.
How it connects
Connects substantial modification to intended purpose, provider status, conformity assessment, and post-market monitoring.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of AI Governance. The section links point to the parts of the book it draws on.