A foundation model is a large-scale AI model trained on broad data that can be adapted to many downstream tasks; a general-purpose AI system is the deployed product built on top of it. The foundation model vs general-purpose AI distinction is not academic under EU Regulation 2024/1689 (the AI Act): “general-purpose AI model” obligations attach to the model itself under Chapter V, while “AI system” obligations attach to a deployed application under Title III and depend entirely on how that application is used. For a university lab that fine-tunes an open-weight model into a research tool and releases it publicly, which category applies — and when — determines a materially different compliance workload.
The AI Act defines a general-purpose AI model (Article 3(63)) as one that “displays significant generality” and can “competently perform a wide range of distinct tasks”, regardless of how it is placed on the market. A general-purpose AI system (Article 3(66)) is an AI system based on such a model that can serve a variety of purposes, whether used directly or integrated into other systems. The two terms are frequently conflated, but the Act’s compliance architecture depends on keeping them separate.
- What is a foundation model? A working definition
- AI Act definitions: general-purpose AI model vs AI system
- Why the distinction matters for research software
- Worked examples for university labs
- Frequently asked questions
- Compliance implications and what comes next
What is a foundation model? A working definition
A foundation model is an AI model trained on large, broad datasets — often using self-supervised learning — that generalises to a wide range of downstream tasks rather than being built for one narrow purpose. Large language models are the most cited example, but the concept also covers text-to-image, text-to-video, and multimodal models.
The term originated in AI research (Stanford’s Center for Research on Foundation Models coined it in 2021) and is not itself a defined legal term in the AI Act. The Act’s operative category, general-purpose AI model, captures the same phenomenon in enforceable language, and in practice most models researchers call “foundation models” meet that legal definition.
AI Act definitions: general-purpose AI model vs AI system
The AI Act runs two separate regulatory tracks that a research team must understand independently, because passing one does not exempt a project from the other.
The general-purpose AI model track (Chapter V, Articles 51–56) regulates the model layer. Under Article 53(1), providers must draw up technical documentation, inform downstream integrators, publish a training-content summary, and maintain a copyright policy. The Commission’s AI Office guidance is explicit that these “provisions… apply to the model itself, regardless of what is or will be its ultimate use.” Models trained with over 1025 FLOP are presumed to pose systemic risk under Article 51(1)(a), triggering evaluation and incident-reporting duties under Article 55.
The AI system track (Title III, Articles 6–49) regulates the application layer. Obligations here — including the high-risk conformity-assessment regime under Annex III — depend entirely on context of use: what the system does, who it affects, and which domain it operates in. A system built on a fully documented foundation model can still be high-risk; one built on an under-documented model can still sit outside Title III if its use case is low-risk.
Crucially, Article 2(8) excludes “any research, testing or development activity regarding AI systems or AI models prior to their being placed on the market or put into service” from the Act’s scope. This is the single most important provision for university labs: internal experimentation is largely unregulated, but that exemption ends the moment a tool is placed on the market — including released publicly under an open licence.
When does fine-tuning create a new “provider”?
Recital 97 clarifies that a model is still “placed on the market” if its provider integrates it into their own AI system, unless use is purely internal, third parties’ rights are unaffected, and the model carries no systemic risk. The Commission’s guidelines on scope (Section 3.2) add an indicative criterion: a downstream entity that fine-tunes an existing model becomes provider of a new general-purpose AI model once the modification’s training compute exceeds one-third of the original model’s training compute. Below that threshold, the original provider keeps Article 53 responsibility, and the lab’s own duties attach mainly at the system layer.
Why the distinction matters for research software
University labs increasingly build research tools — literature-screening assistants, peer-review triage systems, integrity checkers, grant-matching recommenders — on foundation models. Getting the model/system distinction wrong creates two risks: over-compliance (treating a low-risk tool as needing Annex III conformity assessment) or under-compliance (releasing a public tool without required Article 53 documentation).
Two provisions reduce the burden for academic and open-source releases. First, Article 53(2) exempts providers from the Article 53(1)(a) and (b) documentation duties if the model is released open-source with public weights, architecture, and usage information — though this never extends to systemic-risk models. Second, Recital 109 requires that provider obligations “take due account of the size of the provider,” with simplified routes for SMEs and start-ups, a category many university spin-outs fall into.
Neither exemption touches the AI system track. A tool that screens grant applicants or assesses researcher performance may still fall under Annex III’s high-risk categories regardless of how the underlying model is licensed.
Worked examples for university labs
The scenarios below show how the two tracks diverge depending on what is built and how it is released.
| Scenario | General-purpose AI model duties | AI system duties |
|---|---|---|
| Fine-tunes an open-weight model for internal literature screening only, never released | Not applicable — Article 2(8) research exemption while internal | Not applicable — no placing on the market |
| Releases the fine-tuned model publicly, open licence, weights published; fine-tuning compute under one-third of base compute | Base-model provider keeps Article 53 duties; lab is not a new provider (one-third-compute criterion) | Must assess use case under Title III; low-risk screening unlikely to trigger Annex III |
| Substantially retrains a model (compute over one-third of base) and releases it as a research-assessment tool used in hiring-adjacent decisions | Lab becomes provider of a new general-purpose AI model; full Article 53 duties apply | Likely high-risk under Annex III (employment use); conformity assessment and human oversight required from 2 August 2026 |
Frequently asked questions
Are foundation models general purpose?
Most, but not all. A model must display significant generality and competently perform a wide range of distinct tasks to meet the AI Act’s Article 3(63) definition; models fine-tuned to be narrowly specialised for one domain can fall outside it even if built on a general-purpose base.
Is a chatbot built on a foundation model itself a foundation model?
No. A chatbot is a deployed AI system; the language model behind it is the general-purpose AI model. The chatbot’s obligations run through Title III based on use case, while the model’s obligations run through Chapter V regardless of that use case.
What is the difference between a foundation model and an AI agent?
A foundation model is the underlying trained model; an AI agent is a system that uses one or more models to pursue goals with some autonomy, such as planning or calling tools. Under the AI Act, an agent built on a foundation model is assessed as an AI system, with obligations set by context of use, not by which model powers it.
Compliance implications and what comes next
For research offices evaluating an AI-powered tool before release, four checks separate compliant projects from exposed ones:
- Confirm whether the tool is still covered by the Article 2(8) research exemption, or whether release plans amount to “placing on the market.”
- Calculate whether fine-tuning compute crosses the one-third-of-original-compute threshold that can make the lab a new model provider.
- Check the Article 53(2) open-source exemption conditions — weights, architecture, and usage information must all be public.
- Assess the deployed system separately against Title III and Annex III; model-layer compliance never substitutes for system-layer risk classification.
The compliance calendar is tightening. Prohibited AI practice rules have applied since 2 February 2025, general-purpose AI model obligations since 2 August 2025, and high-risk AI system obligations under Annex III take effect from 2 August 2026 — weeks away for any lab planning to release research software touching employment, education, or other Annex III domains. Labs that map tools against both tracks before release, not after, avoid finding out the hard way through a market-surveillance enquiry. Institutional research administration offices are increasingly the first checkpoint for that mapping.
Leave a Reply