Home / The Brief / Obligations
Obligations July 1, 2026

Fine-tune and you may become the provider: the Article 25 role-shift

Modifying a bought-in system can move the heavier compliance burden onto the deployer.

ANALYSIS — EDITORIAL, NOT THE LEGAL RECORD

A recurring misconception is that buying an AI system from a vendor keeps the buyer in the lighter deployer role. Article 25 says otherwise in three situations.

A deployer, distributor or importer is treated as a provider — and inherits provider obligations — if it puts its own name or trademark on a high-risk system, makes a substantial modification to one, or changes a system's intended purpose so that it becomes high-risk.

For organisations fine-tuning or repurposing foundation models this is the clause to watch. A modification made for a legitimate product reason can quietly transfer the technical documentation, conformity and registration burden from the original vendor onto you, on the same system you thought you were merely deploying.

Sources: Art. 25 · verified 2026-07-16
Analysis is original writing by the euaicompliant desk. Not legal advice — the binding text is on EUR-Lex.
RESOLVE TO THE RECORD
The Act, article by article → Obligations database → Two-calendar timeline → Standards tracker →
MORE FROM THE BRIEF
← Two calendars, one regulation: why most compliance schedules are now wrong The Digital Omnibus on AI is adopted — the compliance calendar just moved →
THE STANDING RULE

Superseded dates are struck through, never deleted. Where a deadline moved, we show both — because a compliance calendar you can't audit is worth nothing.

See both calendars →