Question · EU GPAI Code of Practice

Is the EU GPAI Code of Practice mandatory?

The Code is a voluntary tool, drafted by independent experts and assessed as adequate by the Commission and the AI Board, that GPAI model providers can follow to meet AI Act Articles 53 and 55.

AboutEU GPAI Code of Practice
Legal forceVoluntary; adherence is a recognised way to show compliance with binding AI Act GPAI duties
Applies from2 Aug 2025
Checked21 Oct 2026

01 / The answer

The short answer

No. The General-Purpose AI Code of Practice, published on 10 July 2025, is voluntary. The AI Act's duties for general-purpose AI model providers are mandatory and have applied since 2 August 2025; the Code is one way to show compliance with them. The Commission and the AI Board have confirmed it as an adequate voluntary tool, which gives signatories more legal certainty, but it does not create a legal presumption of conformity. Providers that do not sign must show compliance by other adequate means. Commission fines for breaches of the GPAI duties became possible from 2 August 2026.
EU GPAI Code of Practice · checked 21 Oct 2026

02 / The rule

What EU GPAI Code of Practice requires

The Code is a voluntary tool, drafted by independent experts and assessed as adequate by the Commission and the AI Board, that GPAI model providers can follow to meet AI Act Articles 53 and 55. Signatories include most major model developers; non-signatories must show compliance by other adequate means.

  1. 01Transparency chapter: document each model (Model Documentation Form) and supply it to the AI Office and downstream providers on request.
  2. 02Copyright chapter: adopt a copyright policy, respect machine-readable rights reservations such as robots.txt when crawling, and offer a complaints point.
  3. 03Copyright chapter: take measures to reduce the risk of the model producing copyright-infringing output.
  4. 04Safety and Security chapter (systemic-risk models): adopt a safety and security framework and assess and mitigate systemic risks across the lifecycle.

03 / Records

Records to keep

  1. 01Completed Model Documentation Form per model version
  2. 02Published copyright policy and crawler rights-reservation handling
  3. 03Safety and security framework and model reports (systemic-risk models)
  4. 04Serious incident reports sent to the AI Office

Optional evidence · where Planisphere fits

Keep a record anyone can check

When your team meets a duty, Planisphere can seal the event it reports as a receipt.

01 · Your teamRecord the event

A disclosure shown, a review signed, a model change approved: the event your system reports.

02 · PlanisphereSeal it

The event becomes a sealed receipt, dated and attributed to whoever is signed in.

03 · AnyoneCheck it

Paste the receipt into Verify. No account or key.

A record supports your compliance evidence process. It is not a legal finding or a certification. Systems that call Planisphere's gate API can also hold or refuse an action before it runs.

SOURCES

Go back to the source

PRIMARY

RELATED

Related: EU GPAI Code of Practice: the full guide