Summary As proposed, the Cloud and AI Development Act (CADA) defines frontier AI without a fixed compute threshold to keep the definition technologically neutral and future-proof. Under Article 2(4), frontier AI is determined by whether models "approach, reach or exceed the current state of the art" — a dynamic standard that adjusts automatically as hardware efficiency and algorithms improve. This contrasts with the EU AI Act's quantitative compute presumption for general-purpose AI models with systemic risk, meaning CADA's concept can capture cutting-edge capability even where a model does not meet the AI Act's computational benchmark. CADA is a proposal (COM(2026) 502 final) and is not yet in force.

Detail

As proposed in COM(2026) 502 final, CADA establishes a framework for strengthening the cloud and AI ecosystem and references frontier AI throughout — but it deliberately avoids hard-coded computational thresholds for the term. Understanding why requires examining the definition in Article 2, the rationale for technological neutrality, and how this interacts with the existing EU AI Act.

The definition: dynamic, not static

Article 2(4) of the CADA proposal defines 'frontier AI' as:

"AI models or AI systems built upon such models that can perform a wide variety of tasks and that approach, reach or exceed the current state of the art."

This wording is intentionally qualitative and relative. By anchoring the definition to the "current state of the art," the proposal creates a moving target. As the baseline for high-performance AI shifts due to advances in chip architecture, training methods, or data quality, the scope of frontier AI shifts with it. This is designed to prevent the concept from becoming obsolete shortly after the law would enter into force.

Rationale: future-proofing against hardware progress

The primary driver is the rapid evolution of computational efficiency. The relationship between raw compute and model capability is not linear: algorithmic breakthroughs (such as more efficient attention mechanisms) or hardware innovations (such as specialised AI accelerators) can let a model reach state-of-the-art performance using significantly less compute than earlier generations.

A fixed compute threshold (for example, "models trained on more than X operations") could let providers build highly capable, state-of-the-art models that sit just below the line to avoid classification — a regulatory-arbitrage risk. By using a performance-based concept ("approach, reach or exceed"), CADA's framing would reach any model performing at the cutting edge, regardless of the specific resources used to get there.

This is consistent with the proposal's emphasis on large-scale, cross-sectoral initiatives addressing "grand challenges" of strategic relevance for the Union under Article 6(2), as indicated in Annex I. The focus is on strategic importance and capability, not merely the energy or hardware consumed.

Contrast with the EU AI Act's systemic-risk presumption

It is important to distinguish CADA's frontier AI concept from the systemic-risk classification in the EU AI Act (Regulation (EU) 2024/1689).

Under the AI Act's rules on general-purpose AI (GPAI) models (Articles 51–56), a model is presumed to present systemic risk where the cumulative amount of computation used for its training exceeds a quantitative threshold set in the Act. That is a bright-line, quantitative test, and crossing it triggers additional obligations for systemic-risk GPAI, such as model evaluation, adversarial testing, and serious-incident reporting.

CADA does not replicate that threshold. Its frontier AI concept is performance-based: a model could be "frontier AI" under CADA because it reaches the state of the art, even if its training compute fell below the AI Act's figure. Conversely, a model might exceed the AI Act's compute figure through inefficient training yet not be state of the art in performance.

This divergence means entities must navigate two parallel frameworks:

  1. AI Act: obligations are triggered by the compute-based systemic-risk presumption for GPAI, or by intended use for high-risk AI.
  2. CADA: engagement with the frontier AI framework turns on capability and strategic relevance — for example, recognition as a frontier AI priority project (Article 8) and access to Union computing support (Article 9).

Operational implications for providers

For providers, the absence of a fixed threshold introduces uncertainty. There is no simple "compute > X" self-check. Instead, providers would need to benchmark their models against the evolving state of the art, which requires monitoring industry benchmarks and the competitive landscape.

CADA also creates a recognition route for frontier AI priority projects under Article 8: the Commission may, by decision, recognise projects selected through open calls for expression of interest that support grand challenge 3 set out in Annex I, provided they are pioneering projects focused on scaling up frontier AI, are undertaken by an eligible consortium or legal entity involving at least three Member States, and pool computing time and other resources. The criteria are qualitative, focusing on the project's collaborative, scaling-up role rather than raw compute.

What this means for you

For in-house counsel and compliance officers, the dynamic definition calls for proactive monitoring.

  1. Benchmarking infrastructure. Establish internal processes to assess regularly whether your models "approach, reach or exceed the current state of the art." Static internal metrics will be insufficient; consider industry benchmarking and independent evaluations.
  2. Dual compliance tracking. Keep separate tracks for the AI Act and CADA. A model may face AI Act systemic-risk obligations on compute grounds while, separately, being relevant to CADA's frontier AI priority-project route or computing support. These are distinct regulatory buckets with different obligations.
  3. Evidence retention. Because the concept is relative, you may need to show why a model does not qualify as frontier AI if challenged. Retain performance evaluations, benchmark results, and contemporaneous comparisons against the state of the art.
  4. Monitor delegated acts. The Commission would be empowered to adopt delegated acts under Article 45 — including to amend Annex I, where the grand challenges sit (Article 6(4)). While the Article 2 definition is fixed in the text, the implementation detail and the specific grand challenges may evolve, so watch for Commission guidance on how "state of the art" is applied in practice.

Common misconceptions

Misconception: CADA and the AI Act use the same definition for frontier AI. No. The AI Act uses a compute-based presumption for systemic-risk GPAI; CADA uses a performance-based concept ("state of the art"). A model can be one without being the other.

Misconception: Only models with massive compute footprints are frontier AI under CADA. Incorrect. Because of algorithmic efficiency, a model could be state of the art with less compute than a previous generation's non-frontier model. CADA's concept tracks capability, not just scale.

Misconception: The definition is vague and unenforceable. Although dynamic, it is anchored to observable industry standards. "State of the art" is a familiar concept in technology and patent law, and the Commission can be expected to provide guidance to support consistent application.

Misconception: Frontier AI under CADA triggers the same penalties as high-risk AI under the AI Act. No. CADA focuses on ecosystem-strengthening, computing access, and sovereignty. Its penalties under Article 24 relate to infringements of the sovereignty framework chapter by cloud providers, and are set by Member States as effective, proportionate and dissuasive — not the product-style penalty regime the AI Act applies to high-risk systems.

Official sources

Related

This is general information about a draft EU regulation, not legal advice.