Is a foundation model the same legal term as GPAI?
The Act uses . Use that definition when deciding whether Articles 53 and 55 apply; foundation model is a market term.
If you provide a , Article 53 sets documentation, copyright and training-summary duties.
Models with systemic risk have extra evaluation, risk, incident and cybersecurity duties under Article 55.
General-purpose AI (GPAI) models have a separate legal framework from system risk categories. Check whether you provide the model itself or build an application using someone else's model. Using a supplier's model alone does not make you its model provider.
A provider develops a , or has it developed, and places it on the market under its own name or trademark. A customer, reseller or application developer can have other duties without holding that role.
GPAI duties have applied since 2 August 2025; Commission enforcement powers apply from 2 August 2026. Models placed on the market before 2 August 2025 have a compliance transition to 2 August 2027. The 2026 amendment does not postpone these dates.
A non-EU provider must appoint an EU authorised representative by written mandate before EU market placement, unless the Article 54 qualifying open-source exception applies. That exception is unavailable for models with systemic risk.
The representative checks that Annex XI documentation exists, keeps a copy for 10 years after market placement, provides it to authorities on request and cooperates with them.
Sources (4)
Primary legal text defining providers, general-purpose AI models, systemic risk, and Chapter V obligations.
general-purpose AI model
Commission page explaining that its GPAI guidelines clarify who is expected to follow provider obligations.
clarify the scope of the obligations
Supports third-country GPAI provider appointment, written mandate, verification, cooperation, document-access, and 10-year retention duties.
Supports the statement that the 2026 amendment did not postpone the existing GPAI application and transition dates.
Providers need model technical documentation, information for application developers integrating the model, a copyright policy and a public training-content summary.
The technical file must go beyond a short model card. Annex XI covers purpose, use policies, release method, architecture, parameters, input and output types, licence, training/testing, data sources and preparation, compute, training time and known or estimated energy use where relevant.
Sources (3)
Article 53 and Annexes XI-XII set the baseline GPAI provider documentation, downstream-information, copyright-policy, and training-summary duties.
Obligations for providers of general-purpose AI models
Commission Code of Practice form for organising the model documentation used for Article 53 transparency commitments.
Model Documentation Form
Commission explanatory notice and template for the public training-content summary required by Article 53(1)(d).
Public Summary of Training Content
The Article 53 open-source exception covers only technical documentation and integrator information. The licence must permit access, use, modification and distribution, and parameters, weights, architecture and usage information must be public.
Copyright policy and the public training summary remain required. Models with systemic risk cannot use this exception.
Commission guidance treats a modifier as a provider of the modified model when the change significantly affects generality, capabilities or systemic risk. Fine-tuning alone does not settle that question.
Sources (2)
Article 53(2) states the limited open-source exception and expressly excludes systemic-risk GPAI models from it.
This exception shall not apply
Commission guidance page summarising its position on significant modifications and open-source GPAI conditions.
significant modifications to AI models
A GPAI model has systemic risk if it has high-impact capabilities assessed using appropriate tools, indicators and benchmarks, or the Commission designates it for equivalent capabilities or impact.
Article 51 presumes high-impact capabilities when training compute exceeds 10^25 floating-point operations. If that condition is met or you know it will be met, notify the Commission without delay and within two weeks.
Article 55 adds evaluations, EU-level risk assessment and mitigation, serious-incident tracking/reporting without undue delay, and adequate cybersecurity for the model and its physical infrastructure.
Sources (3)
Articles 51, 52, and 55 define systemic-risk classification, notification timing, and the additional duties for GPAI models with systemic risk.
greater than 10^25
Commission page for the reporting template covering serious incidents involving GPAI models with systemic risk.
serious incidents involving general-purpose AI models
Commission page explaining that the Safety and Security chapter is for GPAI models subject to Article 55 systemic-risk obligations.
Safety and Security
Annex XII information must help application providers understand the model's capabilities and limits and meet their own duties. Include tasks, integration options, use policies, distribution, software/hardware dependencies, versions, architecture, parameters, input/output formats and limits, licence and relevant training, testing and validation data.
For Code of Practice signatories, the Transparency chapter adds access commitments: provide contact details, current documentation for integrators and necessary additional information within a reasonable time. The deadline is no later than 14 days after a request, except in exceptional circumstances.
Sources (2)
Annex XII lists the minimum downstream transparency information for providers integrating GPAI models into AI systems.
Transparency information
Transparency chapter describing model documentation, downstream-provider information, and request handling for signatories.
Providing relevant information
The GPAI Code of Practice is voluntary and has been assessed as adequate by the Commission and AI Board. Providers can use it to demonstrate compliance, or use other permitted routes.
Harmonised standards can provide a presumption of conformity for the obligations they cover. Providers using neither an assessed adequate code nor harmonised standards must demonstrate alternative adequate means for Commission assessment.
The Code is not a copyright safe harbour. Its Copyright chapter states that adherence does not establish compliance with EU copyright law or limit court enforcement.
The Act uses . Use that definition when deciding whether Articles 53 and 55 apply; foundation model is a market term.
Up-to-date technical documentation, information for system developers integrating the model, an EU copyright policy, a public training-content summary using the AI Office template, and cooperation with authorities. Check the limited open-source exception.
When the model is classified as having systemic risk under Articles 51 and 52. Providers then need evaluations and adversarial tests, systemic-risk mitigation, serious-incident reporting and cybersecurity protection.
Sources (3)
Commission page identifying the Code as a voluntary tool, recording the Commission and AI Board's adequacy assessment, and distinguishing the Transparency, Copyright, and Safety and Security chapters.
voluntary tool
Copyright chapter caveat that Code adherence does not itself constitute compliance with Union copyright law.
does not constitute compliance
Articles 53 and 55 explain use of codes of practice, harmonised standards, and alternative adequate means of compliance.
alternative adequate means of compliance
Sorena can help you organise Article 53 evidence and assess whether Article 55 adds duties.
"general-purpose AI model"
"Obligations for providers of general-purpose AI models"
"This exception shall not apply"
"greater than 10^25"
"Transparency information"
"alternative adequate means of compliance"
"voluntary tool"
"Safety and Security"
"scope of obligations"
"clarify the scope of the obligations"
"significant modifications to AI models"
"summary of training content"
"Public Summary of Training Content"
"serious incidents"
"serious incidents involving general-purpose AI models"
"copyright policy"
"does not constitute compliance"
"model documentation"
"Providing relevant information"
"Model Documentation Form"
Clear answers on AI Act scope, risk categories, provider and user duties, general-purpose models, disclosures, rights, assessments and deadlines.
Find the AI Act deadline for your system or model. Check high-risk dates, transparency duties, older-model transitions and the evidence to prepare.
Check who needs an Article 27 fundamental rights impact assessment, what it must contain and how DPIA reuse, notification and registration work.
Collect model documentation, integration information, copyright records and training summaries. Add testing, incident and security records for systemic risk.
Set up high-risk AI monitoring, identify serious incidents and check reporting deadlines, recipients, deployer escalation and corrective action.
Check the AI Act fine tiers, smaller-organisation caps, GPAI provider fines and the facts authorities consider when deciding a penalty.
Check serious-incident harm, preserve evidence and choose the reporting deadline and recipient for high-risk AI systems and systemic-risk GPAI models.
See which AI Act rules apply now and what comes next. Check high-risk dates, older-model transitions and the difference between legal and standards dates.
Compare AI Act legal duties with ISO/IEC 42001 management-system requirements. See which records can be reused and what certification does and does not cover.
Compare AI Act legal duties with the voluntary NIST AI RMF. Map risk records to specific requirements and identify legal steps that need separate evidence.
Use five checks to establish AI Act scope, exclusions, your role, risk categories and evidence for the decision.
Choose between provider-run internal control, notified-body assessment and a product-law procedure before release.
Classify an AI tool or model before purchase or release. Check EU scope, prohibited uses, high-risk rules, transparency and GPAI duties.
Check each AI tool, decide which duties apply, and give every action an owner and evidence link.
Some high-risk systems use a provider-run assessment. Others need an authorised independent assessor or a product-law assessment.
Check whether the AI Act applies to your system or model, identify your provider or deployer role, and keep evidence for the decision.
High-risk providers must meet system requirements before supply. Deployers must use and monitor the system under the provider's instructions.
Check the system's risk controls, data, documentation, logs, instructions, human oversight and testing before release.
Find high-risk AI examples in recruitment, banking, education, healthcare, public services and products. Check Article 6 conditions and exceptions.
Build a compliance plan for each AI tool: your role, the duties that apply, the evidence needed and the person responsible.
Use EN 18286:2026 to organise provider quality-management procedures and keep evidence that they work for each high-risk system.
Build the technical file and provider records for a high-risk AI system, with owners and evidence links for each field.
Check Article 50 chatbot notices, synthetic-output marking, biometric notices, deepfake disclosures and public-interest text exceptions.
Check Article 5 prohibited AI practices, the narrow exceptions, evidence to retain and the new content prohibitions from 2 December 2026.
Check provider, deployer, importer and distributor roles, when changes create provider duties, and how model and system responsibilities differ.
Find the assessment route for high-risk AI, when a notified body is required, and which declaration, CE-marking and registration records you need.
Check whether software counts as AI, how models differ from systems, when embedded AI is high-risk, and which scope and role evidence to keep.
Understand high-risk AI monitoring under Article 72: the provider plan, deployer feedback, logs, corrective action, incidents and change reviews.
See which industry AI uses fall under Annex III, when Article 6(3) can apply, and what providers must document and register.
See what Article 11 and Annex IV require in high-risk AI technical documentation, from system identity and testing to monitoring and retention.
Check general-purpose model duties, systemic-risk classification, open-source conditions, copyright, training summaries, incidents and application dates.
Check AI interaction notices, technical content marking, biometric notices, deepfake and text disclosures, exceptions, accessibility and deadlines.
Check serious-incident outcomes, reporting roles, 15-, 10- and two-day deadlines, authority recipients, corrective action and the separate model route.
Check who needs an Article 27 fundamental rights impact assessment, what it must cover, and how privacy assessments, notification and registration fit.