WARRANTThe 2026-05-07 trilogue · what was agreed.
On the evening of 2026-05-07, in Brussels, Council Presidency negotiators and European Parliament rapporteurs reached a provisional political agreement on the Digital Omnibus on AI. The Commission tabled the Omnibus on 19 November 2025 as part of the broader Digital Omnibus package, which sweeps in revisions to the AI Act, the Data Act, the Data Governance Act, and adjacent digital files. The headline outcome on the AI Act file, in the Council's own framing in press release 299/26, is to simplify and streamline the rules, with two operative effects: a deferral of the application calendar, and a tightening of the transparency calendar.
The Council press release dated 2026-05-07 carries the working summary: Annex III standalone high-risk obligations move from 2 August 2026 to 2 December 2027; Annex I high-risk embedded in regulated products moves from 2 August 2027 to 2 August 2028; AI regulatory sandboxes at national level move to 2 August 2027; the Article 50 transparency grace period falls from six months to three months, putting the operative cut-over at 2 December 2026. A new prohibition is added: AI generation of non-consensual sexual or intimate content and child sexual abuse material.
Provisional agreements in the Union legislative process are political, not legal. They reflect the position of the negotiators in the room. They do not yet reflect the position of the Council as a whole, the Parliament as a whole, or the regulation as enacted. The four downstream steps from provisional agreement to binding law are explicit and sequential. Until those steps completed, the AI Act as published on 12 July 2024 continued to govern; with adoption complete in June 2026, the amended calendar is the operative one.
The five operative changes in the agreed text.
The Council press release of 2026-05-07 sets out five operative changes inside the AI Act file. Each is paraphrased verbatim where the text permits. The political character of the document cautions against quoting language that has not yet completed legal-linguistic revision, but the substantive shape is unambiguous.
What did not change · the in-force layer.
The Omnibus is a deferral instrument. It moves application dates forward in time and reshapes one transparency clock. It does not unwind the parts of the regulation already in force. Three layers of obligation are unaffected by the 2026-05-07 agreement, and any reading of the Omnibus that suggests a wider reset is misreading the political text.
The first layer in force is the 2 February 2025 perimeter. The Article 5 prohibited-practices list applies. The Article 4 AI literacy obligation applies to providers and deployers. Neither moves. The Omnibus adds to the Article 5 list, it does not subtract.
The second layer in force is the 2 August 2025 perimeter. The Articles 53 and 55 obligations on general-purpose AI model providers apply. Article 53(1)(a) technical documentation, Article 53(1)(b) downstream-provider documentation, Article 53(1)(c) copyright policy, Article 53(1)(d) sufficiently detailed training-data summary, and the Article 55 systemic-risk obligations for the largest models, all of these continue to bind. The governance architecture (Article 64 AI Office, Article 65 European Artificial Intelligence Board, Article 67 Advisory Forum, Article 70 national competent authorities) is operative. The penalty regime in Article 99 is operative for breaches of these provisions.
The third layer is Article 6(1). Article 6(1) treats an AI system as high-risk when it is a safety component of a product covered by Union harmonisation legislation listed in Annex I, or is itself such a product subject to third-party conformity assessment. The original timeline for paragraph 1 application was 2 August 2027. The Omnibus moves it to 2 August 2028. Article 6(1) itself, the classification rule, is unchanged.
Why the deferral happened · three operative reasons.
The Commission tabled the Digital Omnibus on AI on 19 November 2025. The political case for a deferral, reading both the Commission's tabling memorandum and the Council and Parliament position papers in the run-up to the 2026-05-07 trilogue, rests on three operative reasons.
First, the Commission missed the 2 February 2025 deadline for the Article 96(1) guidance on the practical implementation of the regulation, including the application of the Article 6 high-risk classification. The original Article 96 timeline anticipated guidance in place a clear eighteen months before the Annex III application date. That cushion was lost. Providers preparing for 2 August 2026 had been working from draft guidance and aggregator paraphrase, not from the Commission's authoritative reading.
Second, the harmonised standards mandated under Article 40 and developed by CEN-CENELEC JTC 21 under standardisation request M/593 are running behind the original publication calendar. As of May 2026, several Type-A and Type-B horizontal deliverables remained in draft. The provider wishing to avail itself of the Article 40(1) presumption of conformity through a harmonised standard could not do so for parts of the Annex IV documentation surface, because the harmonised standards were not in the Official Journal yet.
Third, SME readiness. Article 11(1) explicitly contemplates simplified technical documentation for small and medium-sized enterprises and start-ups, and Article 62 obliges Member States to take SMEs and start-ups into special account. The Council and Parliament received material industry input arguing that the 2 August 2026 date, in the absence of complete Commission guidance and complete harmonised standards, would impose a disproportionate compliance load on smaller providers. The Omnibus's deferral is, in part, a response to that input.
From provisional to adopted · four steps to binding law, three complete.
The provisional agreement reached on 2026-05-07 was a political document. The European Union legislative process turns a political agreement into binding law through four operative steps, in sequence. Three of the four completed in June 2026; publication in the Official Journal is the remaining formality.
The co-legislators completed the endorsement steps well before 2 August 2026, the original Annex III application date. The Digital Omnibus moves the Annex III standalone high-risk application date to 2 December 2027, replacing the old conditional trigger with a fixed date. The Annex III high-risk application date is 2 December 2027, deferred from 2 August 2026 by the Digital Omnibus; adopted: European Parliament 16 June 2026, Council 29 June 2026.
The asymmetry · timing moved, content did not.
The single sharpest reading of the Omnibus is the asymmetry between what moved and what did not. What moved is the application calendar. What did not move is the substantive content of the obligations. Article 12 still binds the provider to technically allow for the automatic recording of events over the lifetime of the high-risk AI system. Article 13 still binds the same provider to ship instructions for use sufficient to enable the deployer to interpret outputs. Article 11 still binds the provider to draw up the Annex IV technical documentation file before placing the system on the market. Annex IV still specifies, in nine sections, what that file must contain.
The asymmetry has a practical implication for any provider that has been preparing for the 2 August 2026 date. The deferral pushes when the obligations bite, not what the obligations require. A provider whose Annex IV file is complete, whose Article 12 logging pipeline is automatic and lifetime, whose Article 13 instructions for use cover all seven mandatory elements, and whose Article 14 human-oversight measures are documented and operative, is ready under any deferred date. The work done against 2026-08-02 is not wasted work. It is work-in-place against 2027-12-02.
The reverse implication is also true. A provider that reads the deferral as a reprieve is misreading it. The Annex III standalone high-risk application date is 2 December 2027 (deferred from 2 August 2026 by the adopted Digital Omnibus), the substantive work is the same either way, and the firm that designs its records early meets the date with evidence that has already run in production.
What this means for Warrant customers · the evidence pattern is unchanged.
Warrant produces evidence packages from AI agent execution traces, each one a record mapped to a specific EU AI Act obligation and independently verifiable without contacting Warrant. The package emits structured fields mapped to specific articles of the AI Act, including Article 12 logging fields, Article 13 instruction-for-use fields, and Annex IV section-by-section field mapping. None of those mappings change as a function of the Omnibus. It does not amend Article 11, Article 12, Article 13, Article 14, Article 15, Article 47, or Annex IV. It moves the date on which they begin to apply to Annex III standalone systems.
For a customer running an Annex III high-risk AI system in production today, the substantive obligations are unchanged from the pre-Omnibus position; only the application date moves. The Annex III standalone high-risk application date is now 2 December 2027 (deferred from 2 August 2026 by the Digital Omnibus; adopted: European Parliament 16 June 2026, Council 29 June 2026). Build to the substantive obligations regardless: the customer that has an evidence package already produced arrives at 2 December 2027 ready, and is also covered should publication framing shift before then.
The same logic applies to the Article 50 transparency obligation, which the Omnibus tightens rather than defers. With the Omnibus adopted, Article 50 applies from 2 August 2026, and the transitional cut-over for systems already on the market is 2 December 2026. Generative-AI providers and deployers should build to 2 August 2026.
Questions a compliance officer asks first.
Read the source directly.
- Council press release 299/26 · Artificial intelligence: Council and Parliament agree to simplify and streamline rules · 2026-05-07
- Regulation (EU) 2024/1689 · the AI Act as enacted · EUR-Lex CELEX:32024R1689
- Article 113 · entry into force and application dates · annotated text
- Article 50 · transparency obligations for generative AI · annotated text
- Warrant register · Article 12, line by line
- Warrant register · Article 13, line by line
- Warrant register · Annex IV, line by line
Authored by Warrant Editorial. [email protected]. Velocity reading on a fast-moving regulatory file. Not legal advice. The 2026-05-07 agreement was adopted by the European Parliament on 16 June 2026 and the Council on 29 June 2026; publication in the Official Journal of the European Union is the remaining formality before entry into force. We will update this entry when publication completes.