惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

大猫的无限游戏
大猫的无限游戏
月光博客
月光博客
博客园 - Franky
博客园 - 三生石上(FineUI控件)
爱范儿
爱范儿
博客园 - 司徒正美
博客园 - 叶小钗
Apple Machine Learning Research
Apple Machine Learning Research
美团技术团队
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
The Cloudflare Blog
B
Blog RSS Feed
阮一峰的网络日志
阮一峰的网络日志
宝玉的分享
宝玉的分享
V
Visual Studio Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
IT之家
IT之家
博客园_首页
S
SegmentFault 最新的问题
A
About on SuperTechFans
Blog — PlanetScale
Blog — PlanetScale
GbyAI
GbyAI
H
Help Net Security
MongoDB | Blog
MongoDB | Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
The EU AI Act Gets a Makeover — And Some Much-Needed Merc...
Pixelwitch · 2026-06-27 · via DEV Community

Pixelwitch

The EU's AI Act is getting its first significant overhaul — and if you've been dreading compliance deadlines, there might be some relief on the horizon.

Council and Parliament have reached a provisional agreement on amendments to Regulation (EU) 2024/1689, announced May 7th, 2026. The changes are partly a response to the European Commission's Digital Omnibus, a broader package aimed at simplifying compliance while strengthening protections. But this isn't just a bureaucratic tweak — there are real substantive shifts here that businesses need to understand.

The Deadline Extensions That Companies Wanted

The biggest win for industry is time. High-risk AI systems under Annex III now have until December 2, 2027 to comply — a 17-month extension from the original timeline. AI systems integrated into products subject to product safety legislation (Annex I) get even more breathing room: until August 2, 2028, a full year extra.

Given how fast the AI landscape is moving, and how complex compliance is proving to be in practice, these extensions are likely welcome across the board. The original timeline was always ambitious. Now it's merely aggressive.

But Don't Get Too Comfortable

While high-risk systems got more time, transparency obligations just got tighter. Providers now have until December 2, 2026 — roughly three months — to implement watermarking and content labelling requirements. That's a reduction from the original six-month grace period, and it's a reminder that Brussels isn't easing off on AI accountability, just reprioritising where pressure gets applied.

There's also a new prohibition worth noting: AI systems that generate harmful content without appropriate safeguards — including non-consensual intimate imagery and child sexual abuse material — are now explicitly banned under Article 5. If you're building generation tools of any kind, this is a red line you do not cross.

SME Relief — Finally

One consistent complaint about the original AI Act was that its compliance burden was designed for large enterprises. Startups and smaller players either couldn't afford the overhead or were spending disproportionate resources on paperwork rather than product development.

The provisional agreement addresses this by extending compliance privileges to a new category: "small mid-cap" organisations — companies with fewer than 750 employees and under €150 million in annual turnover (or a €129 million balance sheet). These include simplified technical documentation requirements and more proportionate penalties for non-compliance.

There's also a new EU-level regulatory sandbox operated by the AI Office, with priority access for SMEs, startups, and small mid-caps. The national sandbox deadline has been pushed back a year to August 2, 2027, but this new EU sandbox is specifically designed to make it easier for smaller players to test and iterate.

What Happens Next

The provisional agreement still needs formal endorsement, legal-linguistic review, and adoption before it becomes law. There's a hard deadline: August 2, 2026. If that passes without formalisation, the original provisions apply instead.

For most organisations, though, the message is clear: use this time wisely. The AI Act isn't going away. The obligations are real, the enforcement mechanisms are being built, and the clock — even with these extensions — is still running.

The big question is whether these amendments represent a genuine effort to make the regulation work better, or just a pressure valve to manage industry complaints. My guess is somewhere in between. Which, in regulatory terms, counts as progress.