Docs

GPAI Code of Practice: systemic risk obligations under Article 55

As of 18 November 2026 · checked against Regulation (EU) 2024/1689 and the Commission Code of Practice page

Information only, not legal advice. This page summarises the Code of Practice and the obligations in Articles 51 to 55. Confirm any compliance decision with qualified counsel.

Articles 51 to 55 of Regulation (EU) 2024/1689 split general-purpose AI models into two tiers: GPAI, and GPAI with systemic risk. The second tier carries materially heavier obligations. The General-Purpose AI Code of Practice is a voluntary tool, endorsed by the Commission, with three chapters: Transparency, Copyright, and Safety and Security. Signatories can rely on it to demonstrate compliance (Art. 53(4) and 55(2)). This page covers what separates the tiers, what Article 55 adds, and how the operational mechanics (notification, model evaluation, incident reporting) actually work.

GPAI vs. GPAI with systemic risk

Every general-purpose AI model is in scope of Article 53. A subset crosses into Article 55. Two paths into the systemic-risk tier:

Once the threshold is met, Article 52(1) requires the provider to notify the Commission without delay and in any event within two weeks of meeting the threshold or, if later, of being aware that it will be met.

The obligations in Article 53 (every GPAI)

What Article 55 adds (systemic-risk tier)

The Safety and Security chapter of the Code translates these four duties into commitments that signatories accept. Adherence is voluntary. Providers who do not adhere must demonstrate alternative adequate means of compliance for assessment by the Commission (Art. 55(2)).

The 14-day notification

Article 52(1) requires notification within two weeks of the model meeting the systemic-risk threshold. The notification:

The Commission publishes and keeps up to date a list of GPAI models with systemic risk (Art. 52(6)).

Model evaluation in practice

Article 55(1)(a) requires evaluation with standardised protocols and tools reflecting the state of the art, including documented adversarial testing. How a signatory plans, runs and repeats evaluations is set out in the Safety and Security chapter of the Code. Read it in the original on the Commission page; this page does not paraphrase its commitments.

Serious incident reporting

The reporting obligation under Art. 55(1)(c) parallels Article 73 for high-risk AI systems but applies to the GPAI provider directly, towards the AI Office. Incident reports themselves are not public. AI Act Radar emits events on the gpai topic when the Commission publishes something about them, such as guidance or enforcement action. Illustrative payload:

{
  "id": "evt_example_gpai_guidance",
  "type": "guidance",
  "source": "aioffice",
  "topics": ["gpai"],
  "severity": "medium",
  "title_en": "AI Office publishes guidance on serious incident reporting for GPAI models",
  "ai_act_articles": ["Art. 55(1)(c)"],
  "url_official": "https://digital-strategy.ec.europa.eu/..."
}

Cybersecurity expectations

Article 55(1)(d) requires an adequate level of cybersecurity protection for the model and its physical infrastructure. Recital 115 names what that protection should consider: accidental model leakage, unauthorised releases, circumvention of safety measures, cyberattacks, unauthorised access and model theft. It suggests securing model weights, algorithms, servers and data sets through operational security measures, cybersecurity policies, established technical solutions, and cyber and physical access controls.

What to track

Sources

→ See live updates: https://aiactradar.com

→ Subscribe to webhook: https://docs.aiactradar.com/quickstart