One act changed three regulations. Most teams saw one.

In July, Regulation (EU) 2026/1744 — the "Digital Omnibus on AI" — was published in the EU's Official Journal. If you follow AI regulation, you saw it: it reshapes the AI Act's high-risk timeline.

What fewer noticed is in the title itself. The same act amends three regulations: the AI Act (2024/1689), the aviation safety framework (2018/1139) — and the Machinery Regulation (2023/1230).

Why the machinery change went unseen.

Most regulatory monitoring is organised by regulation name. Someone owns "AI Act updates". Someone else owns machinery compliance. A newsletter covers sustainability; another covers product safety.

An omnibus act breaks that model. It touches three domains in one stroke — but it gets filed, discussed and searched under one name. The team watching AI caught this act. The team responsible for machinery conformity likely never saw it, because nothing they follow is called "AI".

Cross-regulation amendments are not rare. They are how the EU increasingly legislates: simplification packages, omnibus acts and horizontal frameworks that reach into sector rules. Monitoring organised by regulation name is structurally blind to them.

What actually changed.

For the AI Act, the amendment replaced the previous high-risk timeline with unconditional dates: high-risk systems under Annex III apply from 2 December 2027, and high-risk systems that are safety components of regulated products (Annex I) from 2 August 2028. Which date matters for AI in industrial or energy systems depends on the system's function and product classification.

For the Machinery Regulation, we verified the amending provisions against the new consolidated text. The changes touch specific articles on digital documentation and conformity mechanics — while the application date, 20 January 2027, and the transition from the Machinery Directive are untouched. Sometimes the most valuable finding is confirmation that your dates still hold — established by reading the law, not by assuming.

The part that surprised us.

Verifying against the new consolidated Machinery text surfaced something in our own dataset: a source citation that pointed to the original act — where a date reads differently than in the later corrigendum that corrected it. Our encoded value was right; the evidence link behind it pointed to a version where a reader would find a different number.

We fixed it the same day, and the detection pattern now has a name in our quality checklist. That is what monitoring is for — not just watching the law move, but continuously auditing the evidence behind every value you rely on.

Three takeaways.

• Watch acts, not headlines. Amendments travel under the name of whichever policy area drove them — not the ones they touch.
• Verification beats notification. A signal that something changed is only half the work; the other half is reading the consolidated text and confirming what it means for the values you depend on.
• Your evidence chain ages too. Corrigenda and consolidations can leave your citations pointing at superseded text even when your conclusions are right.