Does this apply to us if we only use these tools?

The heaviest duties sit with whoever provides the model rather than with everyone using one, so an ordinary buyer meets this mostly as documentation they can now ask for. That said, what you build on top and who you serve it to affect your own position, which is a question for counsel rather than for a glossary.

Why did vendors start publishing more about their systems?

Because the obligations attached to this category made it necessary, and because customers began asking. The practical benefit to a buyer is real: accounts of how a system behaves and what it was built from exist now where they did not, and a supplier that cannot produce anything stands out.

How do I tell which sense is being used?

By where you found it. In a product page it is describing flexibility and in a contract, a security questionnaire or a compliance annex it is naming a regulated classification. The words are identical and the information conveyed is not, which is worth a moment's attention when reading either.

Glossary

General-purpose AI

General-purpose AI describes a model built to handle many kinds of task rather than one, and the phrase now does double duty because European regulation adopted it as a category with obligations attached.

In plain terms

A model that can do many different things rather than one specific job. That used to be a plain description of how something was built. European regulation then adopted the phrase as a named category with duties attached, so the same words now appear both in a product description and in a contract, meaning slightly different things.

Why it matters

Because a buyer meets the phrase twice and the second meeting is the consequential one. In marketing it describes flexibility, and in a supplier's paperwork it signals a regulated classification that brings documentation duties, so noticing which sense is in play tells you whether you are reading a capability claim or a compliance position.

How it works

The plain sense describes breadth of capability. A model trained to handle language generally, rather than to perform one narrow task, can be pointed at drafting, classification, extraction and analysis without being rebuilt, and that flexibility is what made a single product useful across departments that share nothing.

The regulatory sense attaches obligations to whoever provides such a model, and this is what changed. Duties around documentation, transparency about training material and the sharing of information with those who build on top now sit with the provider, which is why vendors began publishing accounts of their systems that did not exist before.

The two senses come apart in a way worth watching. A product may be general in the everyday sense while its provider is not the entity carrying the regulatory duty, because the obligations sit with whoever supplies the underlying model rather than with everyone who packages it, so the question of who is responsible for what is not answered by the phrase alone.

For most buyers the practical effect arrives as paperwork rather than as capability. Documentation exists that previously did not, suppliers can be asked for it, and a vendor unable to say anything about the model underneath its product is now conspicuous in a way it was not a few years ago.

The same phrase, two documents

There is a small but real reading skill here that pays off across a lot of vendor material. Terminology that starts as informal description and is later adopted into regulation acquires a second life, and the two lives run in parallel without either signalling which is in play. A marketing page saying a system is general-purpose is making an ordinary claim about flexibility and could equally have said versatile. The same phrase in a supplier agreement or a security questionnaire is doing something quite different: it is placing the product inside a category that carries duties, and it has been chosen by somebody who knew that. Neither use is deceptive. What matters is that a buyer skimming both will read the second in the register of the first, and miss that they have been handed a compliance position rather than a feature list. Noticing the document type is the whole of the technique.

Seen in the wild

A general assistant covering writing, analysis, coding and image work in one place, which is the plain sense of the phrase as a product.
ChatGPT
A compliance platform whose framework coverage now spans AI management standards alongside the traditional security ones.
Vanta
An assistant from a European company offering regional data residency and on-premises deployment, where jurisdiction is the stated differentiator.
Mistral Vibe

Common misconceptions

People assume

It is just a description of a capable model.

In fact

It is that and a named regulatory category, and the second sense carries obligations. When the phrase appears in a supplier's paperwork rather than in its marketing, it is usually doing the legal job, which is worth noticing because the two convey completely different information.

People assume

If our vendor is compliant, we are covered.

In fact

The duties are distributed rather than concentrated. Obligations sit differently on whoever supplies the underlying model and whoever builds a product on it, so a vendor's position does not automatically answer questions about yours, and the phrase itself settles none of that.

Telling them apart

General-purpose AI vs Foundation model

General-purpose AI

Breadth of capability, and now a legal category.

Foundation model

A base others build on, which is a role.

The two describe much the same objects for different reasons, and only one of them appears in legislation.

Questions

Does this apply to us if we only use these tools?: The heaviest duties sit with whoever provides the model rather than with everyone using one, so an ordinary buyer meets this mostly as documentation they can now ask for. That said, what you build on top and who you serve it to affect your own position, which is a question for counsel rather than for a glossary.
Why did vendors start publishing more about their systems?: Because the obligations attached to this category made it necessary, and because customers began asking. The practical benefit to a buyer is real: accounts of how a system behaves and what it was built from exist now where they did not, and a supplier that cannot produce anything stands out.
How do I tell which sense is being used?: By where you found it. In a product page it is describing flexibility and in a contract, a security questionnaire or a compliance annex it is naming a regulated classification. The words are identical and the information conveyed is not, which is worth a moment's attention when reading either.