Urgent.News

What's breaking now, across thousands of outlets.

Tech

The EU Machinery Regulation applies on 20 January 2027, not 14 January

If you are building anything that puts a learned policy in charge of a safety function, the date you need is 20 January 2027. A lot of secondary sources say 14 January. They are reading the original text. Regulation (EU) 2023/1230 as published did say 14 January. The Corrigendum of 4 July 2023, OJ L 169, corrected the dates in Articles 6, 47 and 50 to 54. The consolidated text applies from 20…

The EU Machinery Regulation is set to take effect on 20 January 2027, not on the previously reported date of 14 January. This information is derived from Regulation (EU) 2023/1230, which originally indicated 14 January. However, a Corrigendum issued on 4 July 2023, published in OJ L 169, corrected the dates in Articles 6, 47, and 50 to 54. The consolidated text now applies from 20 January 2027.

For software developers, a significant change is that Annex I of the regulation now includes safety components with self-evolving behavior in the conformity assessment process. This is particularly relevant for systems where a "keep-out zone" is enforced by a model rather than a relay.

However, it's important to note that no compliance is required under the EU AI Act's Article 15 obligations for embedded AI at this time. This is a deferred obligation until 2028. Additionally, no insurers have been found to request such compliance at present.

While there may be a business case to undertake such compliance now due to cost savings, it's crucial to understand that the system is currently non-compliant. The information provided is based on primary sources and the corrigendum, and it's not legal advice. For more details, you can refer to https://www.provael.com/regulatory-clock/.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Your app went viral. Adding servers made it worse. Here's why.

It's midnight, someone huge shares your app, 100,000 people show up — and the page dies. You add three servers. It gets worse .

  • 100,000 users caused app crash at midnight
  • Database bottlenecks revealed by request tracing
  • Indexing query and caching recommended to optimize

My audit printed 0 of 0 and called it a pass

Three of the phases in my audit printed this: clusters=0 files=0 judged=0/0 open=0 claim=AHEAD verdict_file=absent Nothing had been examined. No verdict file existed.

  • Audit phases reported as ahead with zero output
  • Verdict of ahead declared despite empty run
  • Proposed fix: add void state for unmeasured phases

More from Saturday 12 September →