GUIDA TECNICA

The EU General-Purpose AI Code of Practice

The EU General-Purpose AI Code of Practice is a voluntary tool published in July 2025 to help GPAI providers demonstrate how they meet AI Act obligations.

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 The EU General-Purpose AI Code of Practice
  5. Metterlo in pratica
  6. Continua a esplorare
  7. Domande frequenti

Panoramica

It has transparency, copyright, and systemic-risk safety and security chapters; providers may instead show compliance through other adequate means or harmonised standards.

Immersione profonda

Article 56 of the EU AI Act encourages the AI Office to facilitate codes of practice that support proper application of the Regulation. The General-Purpose AI Code of Practice was published on July 10, 2025, after independent experts and stakeholders developed its text. It has three chapters: Transparency and Copyright for GPAI providers generally, and Safety and Security for providers of models with systemic risk. The Commission’s current page lists signatories and states that the code is an adequate voluntary tool. The code translates duties into practical documentation and processes. Its Transparency chapter supports information providers must keep or give downstream developers, while the Copyright chapter supports the required policy for complying with EU copyright law and rights reservations. The Safety and Security chapter offers practices for systemic-risk evaluation, assessment, mitigation, incident handling, and cybersecurity. It is not a general AI-system code and does not replace Article 53 or Article 55. Signing is voluntary. Under Articles 53(4) and 55(2), providers may rely on an approved code to demonstrate compliance until harmonised standards are published. A provider that does not adhere to an approved code or applicable standard must demonstrate alternative adequate means for Commission assessment. Following the code is therefore a route to show compliance, not a product certificate, blanket authorization, or immunity from enforcement. Regulation (EU) 2026/1744 amended Article 56 to require the Commission and the AI Board to monitor codes and assess whether they adequately cover the GPAI obligations, with public assessment. The current Commission page reports its status through July 31, 2026. Providers should verify the latest approved version, signature status, and standards when planning compliance. This is an informational overview, not legal advice.

Implementazione nel mondo reale

A provider signs the Transparency and Copyright chapters and uses the model documentation form to organize Article 53 evidence.

A systemic-risk provider compares its safety framework and incident process with the Safety and Security chapter before deciding whether to sign.

A provider that does not sign builds an alternative-compliance record because the Act still applies.

A compliance lead checks Commission updates on code adequacy, signatories, and harmonised standards rather than treating a past signature as permanent approval.

The Future of The EU General-Purpose AI Code of Practice

The Code of Practice may be updated as standards and implementation evidence develop. Regulation (EU) 2026/1744 makes adequacy review and ongoing monitoring explicit, so provider reliance should track the Commission’s current assessment. Providers can prepare an alternative compliance case if they do not sign or if a chapter fails to cover a specific duty. Check the current AI Office page before each major compliance review. Monitor any assessment published after the Commission’s latest review. Check the current Code before renewal.

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 The EU General-Purpose AI Code of Practice 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 The EU General-Purpose AI Code of Practice?

The EU General-Purpose AI Code of Practice is a voluntary tool published in July 2025 to help GPAI providers demonstrate how they meet AI Act obligations. It has transparency, copyright, and systemic-risk safety and security chapters; providers may instead show compliance through other adequate means or harmonised standards.

When was the General-Purpose AI Code of Practice published?

The Commission states that the final GPAI Code of Practice was published on July 10, 2025.

Which chapters are in the GPAI Code of Practice?

The Code has Transparency and Copyright chapters and a Safety and Security chapter for systemic-risk models.

Who is the Safety and Security chapter relevant to?

The Commission says the Safety and Security chapter concerns the additional obligations for systemic-risk GPAI providers.

Which statement describes the legal status of signing the GPAI Code?

The code is voluntary; providers may rely on it for covered obligations or demonstrate alternative adequate means.

What may a provider that does not follow an approved Code or harmonised standard need to show?

Articles 53(4) and 55(2) require providers using another route to demonstrate alternative adequate means for assessment.