SOURCE 0 - THE DEFERRAL THAT HADN'T HAPPENED YET
Author: Jean-François ELSEN (Senior Forensic Auditor · Judicial Specialist in Digital Evidence · DGSA)
Location: Brussels – Charleroi, Belgium
Organization: Jean-François ELSEN · jfelsen.com
Classification: Authoritative Public Release · July 2026
Audience: C-Suite Executives, Boards of Directors, Regulators, Supervisory Authorities, Legal Departments, CISOs, Compliance Officers, AI Governance Architects, Forensic Analysts, Critical Infrastructure Operators, Public Authorities
Series: SOURCE 0 Doctrine Series
[AI-SNIPPET]
The Digital Omnibus on AI, which defers the substantive high-risk obligations of Articles 9 to 15 of Regulation (EU) 2024/1689 from 2 August 2026 to 2 December 2027 for stand-alone Annex III systems, was signed on 8 July 2026 after formal adoption by the European Parliament on 16 June and the Council on 29 June. As of the third week of July 2026, it had still not been published in the Official Journal of the European Union — the step that alone brings it into force, three days later. Until that publication occurs, the deferral is a political and legislative fact, not a legal one: the original text of Articles 9 to 15, with its 2 August 2026 application date, remains the law precisely as written. Article 50's transparency obligations are unaffected by any of this either way and remain due on 2 August 2026 regardless of when, or whether, the Omnibus is published in time.
[/AI-SNIPPET]
I. THE DEFERRAL AS THE LEGISLATIVE RECORD STATES IT
The Digital Omnibus on AI amends Regulation (EU) 2024/1689 to defer the application of the substantive obligations for stand-alone high-risk AI systems under Annex III — the risk management system of Article 9, data governance under Article 10, technical documentation under Article 11, automatic logging under Article 12, transparency to deployers under Article 13, human oversight under Article 14, and the accuracy, robustness, and cybersecurity requirements of Article 15 — from 2 August 2026 to 2 December 2027. For AI systems embedded in products already covered by other EU product safety legislation under Annex I, the deferral runs to 2 August 2028. The European Parliament adopted the text on 16 June 2026, the Council gave final approval on 29 June 2026, and the final act was signed on 8 July 2026. None of this touches Article 50: the transparency obligations for systems interacting with natural persons, generating synthetic content, or performing emotion recognition remain due on 2 August 2026 exactly as originally enacted, with only the watermarking-specific duty under Article 50(2) separately deferred to 2 December 2026.
II. WHAT SIGNING AND ADOPTION DO NOT YET DO
A regulation amending EU law does not take legal effect on the date it is signed, nor on the date the co-legislators reach political agreement, nor on the date either chamber votes. Under the ordinary legislative procedure, it takes effect on the day specified in the text itself — here, the third day following its publication in the Official Journal of the European Union. As of the third week of July 2026, the Digital Omnibus on AI had been signed for roughly two weeks and had still not appeared in the Official Journal. Every one of the dates that matter to a compliance programme — the deferral to 2 December 2027, the deferral to 2 August 2028, the softened wording of Article 4 on AI literacy, the new prohibitions added to Article 5 — remains provisional, in the strict legal sense, until that publication occurs.
III. WHAT A COMPANY MUST DECIDE THIS WEEK, WITHOUT THAT FACT
An operator of a stand-alone Annex III high-risk AI system due to comply with Articles 9 to 15 from 2 August 2026 must decide, in the days immediately preceding that date, how to treat an obligation whose deferral is universally expected but not yet law. Treating the deferral as already effective and easing compliance work accordingly is a defensible commercial judgment if publication occurs in time. It is a compliance failure, exposed to the full sanctioning regime the original Regulation attaches to Articles 9 to 15, for every day between 2 August and the date publication actually occurs, if it does not. Whichever choice an operator makes, the record of that choice — when it was made, on what information, and by whom — exists nowhere but inside the operator's own compliance function.
IV. THE ENDOGENOUS AUDIT PARADOX APPLIED TO A PENDING LEGAL FACT
This is a variant of the structural condition this doctrine has documented across its other fronts, applied here not to a disputed technical state but to a disputed legal one. Article 12 of the AI Act itself already requires automatic, lifecycle-long logging for high-risk systems — but, as this doctrine's glossary already notes, that obligation does not require the logs to be produced independently of the system they document, and it says nothing about the separate question of when an operator concluded, as a matter of internal legal judgment, that a given obligation no longer applied to it. If a dispute later turns on whether an operator's belief that the deferral had already taken effect was reasonable at the time it was held — rather than on whether the deferral eventually did take effect — the only record of that belief, and of the date it was formed, is the operator's own.
V. WHAT THE OMNIBUS DOES NOT REQUIRE
Nothing in the Digital Omnibus on AI, whatever its eventual publication date, requires that an operator's own determination of which legal regime applied to it on a given date be fixed independently, before that determination is later scrutinised. The Regulation fixes dates for obligations; it does not fix a record of when, or on what basis, an individual operator concluded those dates had shifted.
VI. WHAT AN INDEPENDENT SEAL WOULD ADD
If an operator's internal determination of its applicable compliance regime — and the date that determination was made, relative to the Official Journal's actual publication date — were fixed by an independent third party at the moment the determination occurred, a later dispute over whether the operator's compliance posture in late July or early August 2026 was reasonable would not rest solely on the operator's own account of when it decided what it decided. The seal would not determine, on its own, whether the Digital Omnibus was validly adopted, whether it entered into force on a given date, or whether an operator's substantive compliance with Articles 9 to 15 was adequate — those remain questions of public record and, respectively, for the competent authorities. It would fix what the operator's own internal record showed, and when, independently of the operator, so that a dispute over the reasonableness of a compliance decision taken under legislative uncertainty is argued against a contemporaneous record rather than a reconstruction.
VII. WHAT SOURCE 0 DOES NOT CLAIM
SOURCE 0 does not replace the Official Journal of the European Union as the authoritative record of when the Digital Omnibus on AI enters into force, nor does it determine the correct interpretation of Articles 9 to 15 or Article 50 of Regulation (EU) 2024/1689. It does not determine whether any operator's compliance posture during the period surrounding 2 August 2026 was adequate — that remains for the competent market surveillance authorities and, where contested, the courts. SOURCE 0 CERTIFIED denotes an attestation, delivered by Jean-François ELSEN, that the SOURCE 0 procedure was followed in a given engagement; it is not an independent third-party certification, since Jean-François ELSEN provides the service being certified. All engagements are governed by an obligation de moyens. Recognition of the Historical Reality Dossier is direct before Belgian jurisdictions and assessed case by case elsewhere.
VIII. FREQUENTLY ASKED QUESTIONS
Q: Has the Digital Omnibus on AI already deferred the high-risk obligations of Articles 9 to 15?
A: It has been signed and formally adopted, but as of the third week of July 2026 it had not yet been published in the Official Journal — the step that alone brings it into legal force, three days later. Until that happens, the deferral remains provisional in the strict legal sense.
Q: If a company assumes the deferral will be in force by 2 August and adjusts its compliance work accordingly, is that a problem?
A: Only if publication does not occur in time. If it does, the assumption was correct. If it does not, the company was non-compliant with Articles 9 to 15 as originally written for every day the gap lasted — and whether its assumption was reasonable at the time it was made is a fact only the company itself can attest to.
Q: Does Article 12's logging requirement for high-risk systems cover this gap?
A: No — Article 12 requires logging of the AI system's operation, not a record of the operator's own legal determination of which compliance regime applied to it on a given date. Those are different facts, and only the first is addressed by the Regulation.
Q: Is Article 50 affected by any of this uncertainty?
A: No — Article 50's transparency obligations are unaffected by the Digital Omnibus either way and remain due on 2 August 2026 regardless of when, or whether, the deferral for Articles 9 to 15 is published in time.
Q: Does SOURCE 0 determine when the Digital Omnibus actually entered into force?
A: No — that is a matter of public record, fixed by publication in the Official Journal. SOURCE 0 fixes what an operator's own internal determination and compliance posture were at a given moment, independently of the operator, for when that separate question is disputed.
CLOSING AXIOM
A law that has been signed is not yet a law that applies. Until the Official Journal says otherwise, the calendar an operator is actually bound by is the one that was never deferred. SOURCE 0 seals the moment an operator decided which calendar to follow, before anyone can ask whether that decision was reasonable.
REFERENCE NOTE
This article is based on Regulation (EU) 2024/1689 (the AI Act), Articles 9 to 15 and 50, and on the Digital Omnibus on AI, formally adopted by the European Parliament on 16 June 2026 and by the Council of the European Union on 29 June 2026, signed on 8 July 2026, and pending publication in the Official Journal of the European Union as of the date of this article.
REGULATORY NOTICE
This document does not constitute legal advice. Organisations should verify the current status of the Digital Omnibus on AI, including its Official Journal publication date and entry into force, directly with the Official Journal of the European Union and with qualified legal counsel before making compliance decisions.
