Fifty-five days

On May 7, negotiators from the European Council, Parliament, and Commission reached a provisional agreement on the Digital Omnibus on AI. The first set of amendments to the EU AI Act since its adoption in June 2024. The package is public now. Most of the coverage focused on the deferral of high-risk AI system obligations by sixteen months. Buried lower in the document is a detail that matters more for anyone generating video with a text box.

The Article 50 transparency deadline still lands August 2, 2026. Fifty-five days from today. Any AI system deployed after that date must comply with disclosure requirements as they stand. But the watermarking obligation for existing systems, the part that requires machine-readable markers embedded in the output so that generated content can be automatically detected, got pushed back four months. From August 2 to December 2.

The regulation told the industry to label its output. Then deferred the mechanism for doing so.

The gap between wanting and having

Article 50 has two moving parts. The first is the deployer obligation: anyone who publishes AI-generated content must disclose that fact. The second is the provider obligation: the AI system itself must embed machine-readable watermarks, imperceptible markers, and metadata so the content can be detected as synthetic after the fact. The first is a behavior. The second is infrastructure.

The behavior stays on schedule. The infrastructure gets four more months.

For the 122 days between August 2 and December 2, disclosure runs on the honor system. Platforms, publishers, and filmmakers must say "this was generated by AI" while the technical systems designed to verify that claim are still being standardized. C2PA provenance metadata exists. Google's SynthID exists. Neither is universally adopted, interoperable across platforms, or tested at the scale the regulation demands.

The regulation wants something it does not yet have the tools to enforce. This should sound familiar. A hundred and one articles about wanting a specific shot and not having the vocabulary to describe it. The gap between intent and execution is the gap this series lives in. The EU is discovering its own version.

New systems, old systems

The deferral is not a blanket extension. It applies only to AI systems placed on the EU market or put into service before August 2, 2026. Systems deployed after that date must comply with the watermarking requirements from day one.

This creates a two-tier market. Kling, Veo, Runway, Seedance, WAN, Grok Imagine, BACH, HappyHorse: all currently on the market, all qualifying for the December 2 watermark deadline. A model that launches on August 3 does not. The incumbents get a grace period. The newcomers face the full obligation immediately.

For filmmakers, the practical effect is minimal in the short term. The generation models will embed whatever metadata their providers implement, and most major providers are already using C2PA or SynthID. The metadata travels with the file whether the regulation requires it or not. What changes is the legal weight of that metadata. After August 2, the absence of disclosure becomes enforceable. After December 2, the absence of watermarking does too. Fifteen million euros or three percent of global annual turnover. Whichever is higher.

The money got real while the standard got deferred.

Two new prohibitions

The Omnibus added something the original AI Act did not have: criminal prohibitions specific to AI-generated content. Two of them.

The first prohibits AI systems that generate or manipulate realistic depictions of an identifiable person's intimate parts or of an identifiable person engaged in sexually explicit activities without that person's freely given, specific, informed, unambiguous, and explicit consent. The adjectives stack. Freely given. Specific. Informed. Unambiguous. Explicit. Five words that describe a standard no casual generation workflow meets.

The second prohibits AI systems that generate child sexual abuse material.

Both take effect December 2, 2026. Both apply to providers (if the system is designed for this purpose or if such output is a "reasonably foreseeable and reproducible outcome" without significant technical modification) and to deployers (if they use the system for that purpose, including by circumventing safety measures). Accidental generation is expressly excluded for deployers.

These are not disclosure requirements. These are prohibitions. The AI Act started as a risk-classification framework. The Omnibus added its first bans on specific generated output. The regulation is no longer only asking who made the creative decisions. It is declaring that some decisions are not creative at all.

The editorial exemption holds

Article 74 in this series covered the editorial exemption that sits at the heart of Article 50: no label is required if the AI-generated content "has undergone a process of human review or editorial control" and a natural or legal person holds editorial responsibility. The Omnibus did not touch this exemption. It survived the first round of amendments unchanged.

This matters because the exemption is where filmmakers live. A filmmaker who generates clips, reviews them, selects the ones that serve the scene, color grades them, composites them into a sequence, and takes credit exercises editorial control. A social media manager who posts the first output from a chatbot does not. The regulation still draws its line at the same boundary this series has documented: the presence or absence of human creative decisions shaping the output.

The disclosure deadline sharpens this distinction. After August 2, every piece of AI-generated content published in the EU without disclosure and without editorial oversight is in violation. The filmmaker who exercises structured vocabulary, iterates across takes, and takes editorial responsibility produces work that satisfies the exemption. The filmmaker who accepts the first output and posts it does not.

Same model. Same weights. Different legal obligations. That sentence has appeared before. The regulation keeps proving it.

Regulation in pieces

The AI Act was adopted in June 2024. The prohibited practices took effect February 2025. The transparency obligations hit August 2026. The high-risk system obligations, originally scheduled for August 2026, just got pushed to December 2027. The watermarking standards for existing systems moved from August to December 2026. The new prohibitions on intimate imagery arrive December 2026.

No single date. No single obligation. The regulation arrives the same way the technology did: in stages, with each stage revealing what the previous one missed. The prohibitions arrived because the risk classification did not cover them. The watermark deferral arrived because the standard was not ready. The editorial exemption survived because the regulators understood that the interesting question was never "did AI touch this?" but "did a human decide what this looks like?"

The institutional gradient this series has tracked now runs eleven deep. Copyright requires authorship. The Academy requires demonstrated performance. The EU requires disclosure unless editorial oversight was exercised. The Golden Globes require human contributions to remain primary. The Human Made Mark certifies zero AI. China gatekeeps distribution. YouTube auto-detects and labels. SAG-AFTRA requires significant additional value. The DGA contract, twenty-two days from expiration, will add a tenth labor-specific framework. Film schools are embedding corporate tools into curricula. And the EU Omnibus just added criminal prohibitions alongside the transparency obligations, creating the first AI content that is not just labeled or exempted but outright banned.

Each institution answered the same question differently. Each answer arrived on a different schedule. None of them waited for each other.

What fifty-five days means

For filmmakers with structured vocabulary who exercise editorial control, August 2 changes nothing about the practice. The exemption applies. The work satisfies every institutional test because the work was always about making creative decisions rather than accepting defaults.

For the platforms, August 2 is a compliance milestone. Disclosure must be present. Metadata must be embedded in new systems. The penalties are enforceable. The standards are still forming.

For the factory, August 2 is a problem. Fifty thousand AI microdramas a month on Douyin, each published without editorial oversight, each now requiring disclosure if it reaches a European viewer. The extraterritorial scope of the regulation means the rules apply if the content is "used in the Union," regardless of where it was generated. The Chinese content factory just acquired European disclosure obligations it probably has not read.

The regulation split the deadline because the infrastructure was not ready. The intent preceded the mechanism. The institutions wanted labeling before the watermarks were standardized, disclosure before the detection was reliable, prohibitions before the enforcement was tested.

That gap between wanting and having is the oldest theme in this series. A filmmaker wants a specific shot. The text box wants forty words of precise vocabulary to deliver it. A regulator wants labeled content. The watermarking standard wants four more months. The distance between intent and execution does not shrink because someone set a deadline. It shrinks because someone does the work.

Fifty-five days. The label is arriving. The infrastructure is following. The vocabulary, as always, is the part nobody can legislate into existence.

Bruce Belafonte is an AI filmmaker at Light Owl. He has read more regulatory amendments this year than screenplays and considers the ratio a sign of the times.