2026 marks the European Union AI Act's real enforcement start: the AI Office gains fining power over general-purpose AI on August 2, while high-risk system deadlines are pushed to 2027 and 2028. California activates two new laws on January 1 covering frontier-developer safety disclosure and training-data transparency. The federal government moves the opposite direction, ordering a Justice Department task force to challenge state AI laws, naming California's SB 53 as a target.
What Marks August 2, 2026 as the EU AI Act's Real Enforcement Start?
The European Union's AI Office gains full enforcement and fining power over general-purpose AI (GPAI) models on August 2, 2026 — the actual turning point for penalties, even though GPAI provider obligations first applied a year earlier, on August 2, 2025CITE:E2. Models whose training run exceeds 10^25 cumulative FLOP are presumed to carry "systemic risk" under the Act, placing them inside the AI Office's direct oversight once its fining authority activatesCITE:E2.
At the same time, the European Union pushed back its own high-risk enforcement calendar. Under the Digital Omnibus (Regulation (EU) 2026/1744), which took effect in July 2026, obligations for standalone high-risk systems (Annex III) move from the original August 2, 2026 deadline to December 2027, and obligations for high-risk systems embedded in products (Annex I) move to August 2028CITE:E3. The European Union cited unfinished harmonized standards and conformity-assessment infrastructure as the reason for the delayCITE:E3.
| EU AI Act track | Original deadline | Status after Digital Omnibus |
|---|
| GPAI enforcement/fining power | August 2, 2026 | Unchanged — takes effect as plannedCITE:E2 |
| Standalone high-risk systems (Annex III) | August 2, 2026 | Delayed to December 2027CITE:E3 |
| Embedded high-risk systems (Annex I) | August 2, 2026 | Delayed to August 2028CITE:E3 |
How Large Are the EU AI Act's Penalties for Prohibited AI Practices?
Violations of prohibited AI practices under Article 5 carry fines up to €35 million or 7% of a company's global annual turnover from the prior financial year, whichever is higherCITE:E1. Other obligations, including high-risk and transparency duties, cap at €15 million or 3% of global annual turnoverCITE:E1.
| Violation category | Maximum fine |
|---|
| Prohibited AI practices (Article 5) | €35 million or 7% of global annual turnoverCITE:E1 |
| Other obligations (high-risk, transparency) | €15 million or 3% of global annual turnoverCITE:E1 |
How Do California's SB 53 and AB 2013 Work Together?
California's SB 53 Frontier AI Transparency Act and AB 2013 training-data disclosure law both took effect on January 1, 2026, covering different parts of AI developmentCITE:E4CITE:E5. SB 53 applies to "large frontier developers" whose models are trained with 10^26 FLOP or more of compute and whose corporate group reports over $500 million in annual revenue, requiring them to disclose safety frameworks, with violations enforced by the state Attorney General up to $1 million per violationCITE:E4. AB 2013 separately requires generative AI developers to post a "high-level summary" of the training datasets used since January 2022 on their websites before releasing a system to the public, covering data sources and whether the data included copyrighted material or personal information and how it was obtained and processedCITE:E5.
How Is the Federal Government Pushing Back Against State AI Laws?
The Trump administration rescinded the Biden-era AI executive order in 2025 as part of a deregulatory shift, then issued a new executive order in December 2025 directing the Department of Justice to establish an "AI Litigation Task Force" within 30 days to challenge state AI laws on grounds including interference with interstate commerce and federal preemptionCITE:E6. California's SB 53 is identified as a potential target of that task forceCITE:E6.
How Different Are the Compute Thresholds Triggering EU and California Oversight?
The European Union's systemic-risk presumption applies to models trained above 10^25 FLOP, while California's SB 53 sets its large-frontier-developer threshold at 10^26 FLOP — ten times higher — combined with a $500 million group revenue testCITE:E2CITE:E4.
| Jurisdiction | Compute threshold | Additional criteria | Penalty structure |
|---|
| EU AI Act (GPAI systemic risk) | Above 10^25 FLOP | None specified | AI Office fining power from August 2, 2026CITE:E2 |
| California SB 53 | 10^26 FLOP or more | Group revenue over $500 million | Up to $1 million per violation, enforced by Attorney GeneralCITE:E4 |
This represents what the outline frames as standard fragmentation: a developer training near the 10^25–10^26 FLOP range must track two different thresholds, two different regulators, and two different effective dates within the same calendar year.
What This Means
The European Union activates GPAI fining power on August 2, 2026, even as it delays its own high-risk system deadlines to 2027 and 2028CITE:E2CITE:E3. California moved in the opposite direction on enforcement timing, activating both SB 53 and AB 2013 on the same day, January 1, 2026CITE:E4CITE:E5. The federal government's December 2025 executive order and 30-day task force mandate point directly at state laws like SB 53, meaning a frontier developer training above 10^26 FLOP with over $500 million in group revenue could face California's disclosure regime and a federal legal challenge to that same regime within the same yearCITE:E6.
Author's Take・EffectStory 編輯部
The two thresholds that matter here are not close: California's SB 53 sets its large-frontier-developer line at 10^26 FLOP plus $500 million in group revenue, while the EU's systemic-risk presumption kicks in a full order of magnitude lower, at 10^25 FLOP, with no revenue test attached. That gap means a mid-sized frontier lab could clear the EU's systemic-risk bar while sitting comfortably under California's compliance obligations, or vice versa depending on corporate structure — there is no single global compute number a developer can design against. The more consequential variable, though, is not the thresholds themselves but whether they survive contact with the federal government's December 2025 task force, which was given 30 days to build a case against state AI laws and has already named SB 53 as a target. The metric worth watching next is simple: does the Department of Justice actually file suit against SB 53, and does that suit land before or after California's Attorney General brings a first enforcement action under it — whichever comes first will settle whether the 10^26 FLOP threshold is a live compliance obligation or a preemption test case.