GUIDA TECNICA

Modelli GPAI con rischio sistemico ai sensi del Regolamento UE sull'IA

The EU AI Act treats a general-purpose AI model as systemic-risk when it has high-impact capabilities or the Commission designates it for equivalent capabilities or impact.

Ascolta questa guidaNarrato dall'IA · ~3 min

In questa pagina3 minuti di lettura
  1. Panoramica
  2. Immersione profonda
  3. Implementazione nel mondo reale
  4. The Future of GPAI Models with Systemic Risk Under the EU AI Act
  5. Metterlo in pratica
  6. Continua a esplorare
  7. Domande frequenti

Panoramica

More than 10^25 training FLOP creates a presumption of high-impact capability, not an unchallengeable classification; systemic-risk providers have extra evaluation, risk-management, incident-reporting, and cybersecurity duties.

Immersione profonda

The AI Act’s systemic-risk category is a subset of general-purpose AI models. Article 51 provides two routes: a model has high-impact capabilities assessed with appropriate tools, indicators, and benchmarks; or the Commission designates it because capabilities or impact are equivalent, using Annex XIII criteria. Training compute above 10^25 floating-point operations creates a presumption of high-impact capability. The number is a threshold in the law and is subject to delegated adjustment; it is not the only way to qualify. Article 52 requires a provider whose model meets the compute condition to notify the Commission without delay, and no later than two weeks after the condition is met or it becomes known that it will be met. The provider may submit substantiated arguments that the model does not, due to its specific characteristics, present systemic risks. The Commission can reject that case or designate a model on its own initiative or following a qualified scientific-panel alert. Commission guidelines describe its interpretation and enforcement approach but are not binding law. Article 55 adds four duties beyond the general GPAI requirements: standardized model evaluation, including documented adversarial testing; assessment and mitigation of possible systemic risks at Union level; documentation and reporting of serious incidents and corrective measures; and adequate cybersecurity for both model and physical infrastructure. These duties are not waived just because a model is distributed under a free and open-source license. Providers can rely on an approved code or harmonised standards while available, or demonstrate alternative adequate means for Commission assessment. GPAI obligations began applying on August 2, 2025. The Commission’s guidance states that its enforcement powers apply from August 2, 2026, and qualifying models already on the market before August 2, 2025 have a compliance transition until August 2, 2027. Providers should track training-compute evidence, expected threshold timing, notification, and any designation decision. This is an overview, not a legal opinion on an individual model.

Implementazione nel mondo reale

A provider forecasts training compute above 10^25 FLOP and prepares the Article 52 notification before the threshold is reached.

A provider crossing the threshold submits evidence with its notification explaining why the model’s specific capabilities do not create systemic risk.

A safety team documents adversarial testing, EU-level risk assessments, incident response, and infrastructure security for a designated model.

A company with an open-source systemic-risk model checks Article 55 duties rather than assuming Article 53’s limited exception covers it.

The Future of GPAI Models with Systemic Risk Under the EU AI Act

The Act empowers the Commission to revise compute thresholds and benchmarks as capabilities and hardware efficiency evolve. A provider should not assume today’s FLOP threshold will remain fixed or that falling below it resolves designation risk. Monitor official Commission guidelines and any delegated acts, and review status when a model’s training run, capabilities, distribution, or deployment context changes. Track delegated updates to Annex XIII and any official changes to the compute presumption. Document threshold calculations consistently across training runs. Review changes before each release.

Metterlo in pratica

Perché è importante

  • Costo e budget. Le decisioni relative all'architettura determinano prestazioni e costi operativi per anni.
  • Decisioni più chiare. La formazione tecnica aiuta i team a scegliere lo stack giusto, non solo quello più nuovo.
  • Controllo di qualità. Migliori scelte ingegneristiche riducono gli incidenti legati all’affidabilità nella produzione.

Attenzione

  • L'ottimizzazione di un benchmark può nascondere debolezze di sistema più ampie.
  • I costi delle infrastrutture e della manutenzione sono spesso sottostimati.
  • Le lacune in termini di sicurezza e osservabilità possono aumentare man mano che i sistemi diventano più complessi.

Prossimi passi

  1. Definire obiettivi di latenza, qualità e costi prima dell'implementazione.
  2. Benchmark in condizioni di carico e dati realistiche.
  3. Monitoraggio dello strumento per errori, deriva e impatto sull'utente.
  4. Preparare percorsi di rollback e risposta agli incidenti prima della scalabilità.

Continua a esplorare

Newsletter gratuita

Ricevi il briefing quotidiano sull'IA

Tre storie verificate sull'IA ogni mattina nei giorni feriali, scritte in un inglese semplice. Gratuito per sempre, senza pubblicità.

Un'email ogni giorno feriale. Disiscriviti con un clic. Non vendiamo né condividiamo mai il tuo indirizzo.

Mettiti alla prova

Take the GPAI Models with Systemic Risk Under the EU AI Act quiz

Feedback immediato su ogni risposta e un certificato condivisibile con un ID verificabile una volta superato un corso.

Inizia il quiz

Sostieni l'istruzione gratuita sull'IA. AI Understanding è un'organizzazione non profit 501(c)(3) — nessun annuncio, nessun paywall, mai. Fai una donazione

Domande frequenti

What is GPAI Models with Systemic Risk Under the EU AI Act?

The EU AI Act treats a general-purpose AI model as systemic-risk when it has high-impact capabilities or the Commission designates it for equivalent capabilities or impact. More than 10^25 training FLOP creates a presumption of high-impact capability, not an unchallengeable classification; systemic-risk providers have extra evaluation, risk-management, incident-reporting, and cybersecurity duties.

Cosa comporta il calcolo di addestramento superiore a 10^25 FLOP ai sensi dell'Articolo 51?

Article 51(2) presumes high-impact capabilities above the compute threshold, while Article 51 and 52 allow other evidence and procedures.

Quale seconda via può portare alla designazione di rischio sistemico oltre alla presunzione basata sul calcolo?

Article 51(1)(b) and Article 52(4) allow Commission designation based on equivalent capabilities or impact using Annex XIII criteria.

Quando un fornitore deve notificare la Commissione dopo che un modello soddisfa o si prevede che soddisfi la condizione di calcolo?

Article 52(1) requires notice without delay and no later than two weeks after the condition is met or known to be expected.

Quale voce è un obbligo dell'Articolo 55 per un fornitore GPAI a rischio sistemico?

Article 55(1)(a) requires model evaluation under state-of-the-art protocols, including documented adversarial testing.

Cosa richiede l'Articolo 55 riguardo agli incidenti gravi?

Article 55(1)(c) requires tracking, documenting, and reporting serious-incident information and possible corrective measures.