RMRisk Mandate · the business risk layer for autonomous systemsriskmandate.ai ↗
EU EU AI Act — Current Textv0.1.3
Composed current text — not authentic. COMPOSED TEXT - NOT AUTHENTIC. This is the EU AI Act (Regulation (EU) 2024/1689) with the Digital Omnibus on AI (Regulation (EU) 2026/1744, in force 27 July 2026) applied by a deterministic, gated parser. Only the Official Journal publications are authentic law; no official consolidated version existed when this was generated. Corrigenda R(01)-R(04) do not correct the English text (verified against CELLAR). Every fragment's derivation chain is available in the source graphs (vault: data/graph/). Not legal advice.
Derivation

eu-2026-1744/art_001/pt_039/a

op replace · level paragraph · enacting-terms position (39) (a) · in force 2026-07-27

Context (enacting terms)

Article 111 is amended as follows:

The instruction (quoted official text)

paragraph 2 is replaced by the following:

Quoted payload (official replacement/inserted text)

2.Without prejudice to the application of Article 5 as referred to in Article 113, third paragraph, point (a), this Regulation shall apply to operators of high-risk AI systems, other than the systems referred to in paragraph 1 of this Article, that have been placed on the market or put into service before the date of application of Chapter III referred to in Article 113, only if, as from that date, those systems are subject to significant changes in their designs. In any case, the providers and deployers of high-risk AI systems intended to be used by public authorities shall take the necessary steps to comply with the requirements and obligations laid down in this Regulation by 2 August 2030.;

Provenance

linkvalue
payload xml sha25625216e551d36cbc6f882b953f3c1cf278e11ada0aa431c7f1410b9aaaf8b4cfc
OJ Formex memberL_202601744EN.000101.fmx.xml
CELLAR / CELEX32026R1744
target resolutiongrammar over enacting terms; cross-checked against payload Formex IDENTIFIER attributes where present (parser-derived)

Affected provisions

eu-2024-1689/art_111/par_002 amended

BEFORE (as published)

2. Without prejudice to the application of Article 5 as referred to in Article 113(3), point (a), this Regulation shall apply to operators of high-risk AI systems, other than the systems referred to in paragraph 1 of this Article, that have been placed on the market or put into service before 2 August 2026, only if, as from that date, those systems are subject to significant changes in their designs. In any case, the providers and deployers of high-risk AI systems intended to be used by public authorities shall take the necessary steps to comply with the requirements and obligations of this Regulation by 2 August 2030.

AFTER (composed current text)

2. Without prejudice to the application of Article 5 as referred to in Article 113, third paragraph, point (a), this Regulation shall apply to operators of high-risk AI systems, other than the systems referred to in paragraph 1 of this Article, that have been placed on the market or put into service before the date of application of Chapter III referred to in Article 113, only if, as from that date, those systems are subject to significant changes in their designs. In any case, the providers and deployers of high-risk AI systems intended to be used by public authorities shall take the necessary steps to comply with the requirements and obligations laid down in this Regulation by 2 August 2030.

WORD-LEVEL DIFF

2. Without prejudice to the application of Article 5 as referred to in Article 113(3),113, third paragraph, point (a), this Regulation shall apply to operators of high-risk AI systems, other than the systems referred to in paragraph 1 of this Article, that have been placed on the market or put into service before 2the Augustdate 2026,of application of Chapter III referred to in Article 113, only if, as from that date, those systems are subject to significant changes in their designs. In any case, the providers and deployers of high-risk AI systems intended to be used by public authorities shall take the necessary steps to comply with the requirements and obligations oflaid down in this Regulation by 2 August 2030.

Check this and report · derivation.json

How to check: compare the quoted instruction and payload above (hash-anchored to the OJ Formex bytes) against the BEFORE/AFTER panes. Two minutes, one provision. Then file the result — "checks out" is worth recording too.