A general-purpose AI model is defined in Article 3(63) of the EU AI Act as an AI model that displays significant generality, can competently perform a wide range of distinct tasks, and can be integrated into varied downstream systems, regardless of how it is placed on the market. A university prototype never placed on the market or put into service falls outside these duties under the Article 2(8) research exemption; the moment that model, or a fine-tuned derivative, is published or supplied to a third party, Article 53 obligations on technical documentation, downstream information, copyright policy, and a training-content summary can attach.
A general purpose ai model is not defined by branding — it is defined by a compute-and-capability test in the Act’s recitals and the Commission’s guidelines. That test matters for universities, because the same model can sit inside the research exemption one day and carry a regulated “provider” obligation the next, depending on what happens to it.
- What is a general-purpose AI model under the AI Act?
- Foundation model vs general-purpose AI vs narrow research tool: the definitional test
- What are the Article 53 obligations for GPAI providers?
- How does the research exemption apply to universities that fine-tune models?
- Answer-first Q&A
- Implications for universities releasing open models
What is a general-purpose AI model under the AI Act?
Under Article 3(63) of the AI Act, a general-purpose AI model is one that “displays significant generality and is capable of competently performing a wide range of distinct tasks… and that can be integrated into a variety of downstream systems or applications.” Recital 98 anchors this operationally: models trained with at least a billion parameters using large-scale self-supervision are presumed to meet the generality bar.
The Commission’s guidelines on the scope of GPAI obligations add a practical marker: an indicative threshold of 10^23 FLOP of training compute, combined with the ability to generate language, images, or video, points to GPAI status. A narrow classifier trained on one labelled dataset for one task — say, detecting a specific cell morphology in a pathology dataset — meets neither bar and is not a GPAI model; it is a narrow AI system governed, if at all, by the Act’s risk-based system rules in Chapters II–IV, not the model-layer rules in Chapter V.
Foundation model vs general-purpose AI vs narrow research tool: the definitional test
“Foundation model” is not a term the AI Act defines — it originates from the 2021 Stanford Center for Research on Foundation Models literature. What most people call a foundation model is simply a species of general-purpose AI model; the Act creates no separate legal category for it and regulates instead at the model layer (Chapter V) and the system layer (Chapters II–IV).
A narrow research tool is not a defined legal term either. It survives through Article 2(8), which states the AI Act “does not apply to any research, testing or development activity regarding AI systems or AI models prior to their being placed on the market or put into service.” The three-way distinction that matters for universities is:
| Category | Legal basis | Obligation trigger |
|---|---|---|
| General-purpose AI model | Article 3(63), Recital 98 | Placed on the market or put into service (any use case, any modality) |
| “Foundation model” (industry term) | No AI Act definition — a subset of GPAI in practice | Same as GPAI: placement on the market |
| Narrow research tool | Article 2(8) exemption | Never triggered while confined to pre-market research, testing or development |
The trigger is not architecture, size, or pedigree — it is whether the model has been placed on the market, defined in Article 3(9) as first supply for distribution or use in the Union, paid or free. A lab training a model for internal experiments stays inside Article 2(8); publishing its weights publicly, or licensing it to a partner, places it on the market and can trigger Article 53.
What are the Article 53 obligations for GPAI providers?
Article 53(1) of the AI Act sets four core obligations for any provider of a general-purpose AI model placed on the EU market, regardless of size or academic status:
- Technical documentation (Article 53(1)(a)) — training/testing processes and evaluation results, available on request to the AI Office and national authorities.
- Information for downstream providers (Article 53(1)(b)) — capabilities, limitations, and foreseeable misuse, so downstream builders can meet their own duties.
- A copyright policy (Article 53(1)(c)) — how the provider complies with EU copyright law and respects rights reservations in training data.
- A public training-content summary (Article 53(1)(d)) — using the Commission’s template, describing what content trained the model.
These obligations have applied since 2 August 2025 under Article 113(b), with transitional rules for pre-existing models under Article 111(3). A heavier tier applies only to GPAI models posing systemic risk — an indicative 10^25 FLOP training-compute threshold under Article 51(1)(a)-(2), costing tens of millions of euros to reach per the Commission — triggering adversarial evaluation, risk mitigation, incident reporting, and cybersecurity duties under Article 55. Almost no university-trained model approaches 10^25 FLOP, so this tier rarely applies academically; base Article 53 duties can still apply well below it.
How does the research exemption apply to universities that fine-tune models?
Universities interact with the GPAI rules from two directions, and conflating them is the single most common compliance error. First, a university training its own large model purely for internal research stays inside Article 2(8) for as long as the model is neither placed on the market nor put into service — a threshold not crossed the moment a paper is published, but more likely triggered by supplying the model for use or distribution.
Second, and less understood, is what happens when a university fine-tunes an existing GPAI model from a commercial lab. Recital 109 and the Commission’s guidelines indicate fine-tuning can make the modifier a “provider” of a new model — but only for the modification, not the underlying base model. The indicative criterion: if fine-tuning compute exceeds roughly one-third of the original model’s training compute, the university takes on provider obligations for that modification, typically discharged by supplementing existing documentation with what changed.
Two further carve-outs matter for university open-model releases:
- The open-source exemption (Article 53(2)) removes the documentation and downstream-information duties (53(1)(a)-(b)) for models released free and open-source with public parameters, weights, architecture and usage information — not the copyright-policy or training-summary duties, and never for a systemic-risk model.
- Downstream system duties are separate. A university embedding a GPAI model in a chatbot, decision-support tool, or admissions-screening application must separately assess that system against the Act’s risk-based rules in Chapters II–IV, whether or not it is also a GPAI “provider.”
Answer-first Q&A
Is general purpose AI the same as generative AI?
No. Generative AI describes output type — models producing text, images, audio or video — while general-purpose AI is a legal classification under Article 3(63) based on generality and integration potential. Most large generative models qualify as GPAI, per Recital 99, but the two terms describe different properties and are not interchangeable in the regulation.
What is an example of general-purpose AI?
Large language and multimodal models generating text, images, or code across many tasks — commonly called foundation models — are the Act’s typical example under Recital 99. A university-trained model only qualifies once it meets Recital 98’s generality and compute markers, not merely because it shares similar architecture.
Is ChatGPT general-purpose AI?
Yes. Widely used commercial assistants built on large generative models meet the Article 3(63) generality test and are treated as general-purpose AI models, subject to Article 53 obligations from their provider. This differs from a university’s narrow, single-task research classifier, which would not meet the same test.
Implications for universities releasing open models
The practical stakes are documentation discipline, not automatic prohibition. A university planning to publish a fine-tuned or original model should map, before release, whether Article 2(8) still applies, whether the one-third fine-tuning threshold has been crossed, and whether Article 53(2)’s open-source exemption covers the intended licence. Institutions publishing under permissive open licences with full weights and architecture disclosure can shed the heaviest documentation duties while still owing a copyright policy and training-content summary — obligations echoing the transparency practices research administrators already apply to funder mandates such as UKRI’s and Horizon Europe’s.
As the AI Office refines its guidelines and the General-Purpose AI Code of Practice — assessed as adequate by the Commission and AI Board in 2025 — becomes the default route to demonstrating compliance, universities treating model-release governance as a standing institutional process, not a one-off legal review, will be best placed to keep publishing openly without falling foul of Article 53.
