There’s a gap between a political handshake and a published legal text. Compliance teams that built
programs on the EU AI Act Digital Omnibus provisional agreement now need to check whether the formal
amending text confirms their assumptions, or revises them.
The provisional political agreement between EU institutions was confirmed in May 2026, as
reported in TJS coverage on May 27. That agreement established the broad
parameters: extended deadlines for high-risk systems, documentation relief for SMEs, confirmed
prohibitions under Article 5. But provisional agreements are negotiating outcomes, not regulatory
text. The proposed amending regulation, reportedly published in the reporting window per legal
analysts, though EUR-Lex confirmation wasn’t available as of publication, is the instrument that compliance
programs actually bind to.
Legal analysts following the Digital Omnibus process have reportedly begun issuing updated guidance
based on the amending text’s release. Per that analysis, compliance teams should verify any
specific deadline figures or classification changes against the official EUR-Lex publication before revising
program timelines, because some provisional-agreement-era assumptions may not survive into the
binding text without modification.
EU AI Act Compliance Planning Status
Three categories of organizations face the sharpest revision pressure. GPAI providers relying on
provisional-agreement interpretations of provider obligations should check whether the final text
resolves the delegated-acts ambiguities or leaves them open. High-risk system deployers who
scheduled conformity assessment timelines against provisional deadlines need deadline-by-deadline
confirmation. SMEs that deprioritized documentation based on reported relief provisions should
verify that relief survived into the final text without qualification.
The catch is that “reportedly published” isn’t the same as EUR-Lex-confirmed. Before any compliance
program revises a deadline or deprioritizes a documentation requirement, the legal team should pull
the actual text. Don’t expect the amending text to be substantially different from the provisional
agreement, that would be unusual at this procedural stage, but the specifics matter when enforcement
is the consequence.
As the May 28 TJS deadline reference established, the prior
compliance planning framework covered the deadline structure from the provisional agreement.
What’s new today is the trigger for formal revision: the proposed amending text’s publication
means programs built on provisional assumptions now have a verification obligation.
Verification
Partial Legal analysts following Digital Omnibus process; EUR-Lex formal publication unconfirmed as of publication Amending text described as 'reportedly published', EUR-Lex confirmation required before compliance programs revise deadlines or deprioritize requirementsThe real question is how many compliance teams built their August 2026 preparedness milestones on
the provisional agreement without scheduling a formal text review. Those teams now have a narrow
window to catch any discrepancies before deadlines become enforcement exposure.
TJS synthesis
The gap between provisional agreement and formal amending text is exactly where
compliance errors accumulate, not from bad faith, but from the reasonable assumption that the
final text will mirror the handshake. History suggests it usually does. The risk is in the edge cases:
a deadline that shifted by 30 days, a documentation exemption that narrowed in scope, a GPAI
obligation that clarified in a direction no one expected. Organizations that treat the amending
text’s publication as a compliance program checkpoint, not just a news event, will have an audit
trail that matters when enforcement begins.