Explorer
Why this object hangs off that object
Every object in this graph has its own address and can be cited on its own. This page shows which objects exist and, once you open one, why it hangs off another: from which source with its locator, through which condition or exception, to which consequence.
Since the last release an obligation states separately who carries the duty and who is merely affected. Filter by duty holder and you get the duties resting on a role; filter by actor and you get everything that is about that role. That difference is visible on purpose.
This is the knowledge layer under the four levels of the assessment. See the four levels.
Filters
Only dimensions the data carries. A dimension without values is absent rather than empty.
Active filters
Objects
20 objects in this selection.
- ActionEditorialv1.0.08 relations
Assign to each obligation the penalty ceiling that belongs to it
praxikon:eu:ai-act:action:article-99-101-map-penalty-tiers
Walk through your obligations register and mark per line which ceiling applies: Article 99(3) for Article 5, Article 99(4) for the role duties enumerated there, Article 25(2) and (4) and Article 50, Article 99(5) for answering information requests, and otherwise the national penalty regime under Article 99(1). Add the Article 101 regime wherever you provide a general-purpose AI model yourself, and the Article 75c regime wherever the AI Office is competent.
Hangs off: Article 99, 100 and 101: the penalty structure per obligation
Editorially reviewed | enforcement, governance
- ActionUpcomingv1.0.03 relations
Run the four verifications of Article 23(1) before importing
praxikon:eu:ai-act:action:run-importer-verification-checklist
Check and record: the conformity assessment has been carried out, the technical documentation exists, the CE marking plus declaration and instructions for use are present, and an authorised representative has been appointed.
Hangs off: Article 23: obligations of importers
Editorially reviewed | value-chain
You are an importer as soon as you, from within the EU, first place an AI system on the Union market that bears the name or trade mark of a party established outside the EU. What counts is not your purchasing role but whose brand is on the system and who first brings it to market.
Editorially reviewed | value-chain
- ControlEditorialv1.0.08 relations
Recording of the factors in Article 99(7)
praxikon:eu:ai-act:control:article-99-101-mitigating-factor-record
The control that ensures the factors which determine the amount of a fine are recorded at the time and not reconstructed afterwards: which technical and organisational measures were in place, when you notified an infringement yourself, how you responded to requests from the authority, and what you did to mitigate the harm suffered by affected persons. Those factors cut both ways, so the same record can also count against you; that is a reason to keep it properly rather than not at all.
Hangs off: Article 99, 100 and 101: the penalty structure per obligation
Editorially reviewed | control, enforcement
- ControlUpcomingv1.0.03 relations
Stop rule and notification route on doubts about conformity
praxikon:eu:ai-act:control:importer-stop-and-notify-control
As soon as you have sufficient reason to consider a system non-conforming or falsified, it does not go to market, and where there is a risk you notify the provider, the authorised representative and the market surveillance authorities.
Hangs off: Article 23: obligations of importers
Editorially reviewed | value-chain
The marking by which a provider indicates that an AI system conforms to the requirements of Chapter III, Section 2 and to other applicable Union harmonisation legislation providing for its affixing.
Placed against the official source | definitions
Any link in the supply chain that makes an AI system available on the Union market and is neither provider nor importer.
Placed against the official source | definitions
Whoever places on the Union market a system bearing the name or trademark of a party established in a third country.
Placed against the official source | definitions
- DefinitionIn forcev1.0.04 relations
Placing on the market
praxikon:eu:ai-act:definition:definitie-in-de-handel-brengen
The first moment a system or model is made available on the Union market, and therefore the trigger for many obligations.
Placed against the official source | definitions
The umbrella term for all six roles in the chain, and not the person operating the controls.
Placed against the official source | definitions
- DefinitionIn forcev1.0.03 relations
Withdrawal of an AI system
praxikon:eu:ai-act:definition:definitie-uit-de-handel-nemen
A measure aimed at preventing an AI system that is in the supply chain from being made available on the market. It stops distribution, not use by existing customers.
Placed against the official source | definitions
- EvidenceEditorialv1.0.08 relations
Register of penalty ceilings per obligation
praxikon:eu:ai-act:evidence:article-99-101-penalty-exposure-register
Per obligation: which ceiling attaches to it and on which provision that rests, whether the level follows from national law and if so from which, and whether the Article 101 or Article 75c regime is added on top. This is the document that shows a board there is no single amount, and that substantiates where you make your controls heavier.
Hangs off: Article 99, 100 and 101: the penalty structure per obligation
Editorially reviewed | enforcement, evidence
- EvidenceUpcomingv1.0.03 relations
Importer dossier with ten-year retention
praxikon:eu:ai-act:evidence:importer-verification-record
Your own archive of the notified body certificate, the instructions for use and the EU declaration of conformity, available for ten years and in a language the authority easily understands.
Hangs off: Article 23: obligations of importers
Editorially reviewed | value-chain
- ObligationApplicablev1.0.020 relations
Article 111(2): legacy high-risk systems and the 2 August 2030 date
praxikon:eu:ai-act:obligation:article-111-legacy-public-systems
High-risk AI systems placed on the market or put into service before the date of application of Chapter III, since the Digital Omnibus 2 December 2027 for Annex III systems and 2 August 2028 for Annex I systems, come under the high-risk requirements of that Chapter only once their design is significantly changed as from that date. This is not an exemption from the whole Regulation: Article 4 and Article 50 keep running. For systems intended to be used by public authorities the carve out falls away entirely: their providers and deployers must in any case comply with the requirements and obligations by 2 August 2030.
Placed against the official source | high-risk, timeline
- ObligationUpcomingv1.0.015 relations
Article 20: corrective actions and duty of information
praxikon:eu:ai-act:obligation:article-20-corrective-actions
A provider that considers, or has reason to consider, that a high-risk AI system it has placed on the market or put into service is not in conformity with the Regulation must immediately take the necessary corrective actions and inform the distributors accordingly, and, where applicable, also the deployers, the authorised representative and the importers. Where that system also presents a risk within the meaning of Article 79(1), the provider must immediately investigate the causes and inform the competent market surveillance authorities and, where applicable, the notified body that issued a certificate under Article 44.
Placed against the official source | high-risk-requirements, post-market
- ObligationUpcomingv1.0.011 relations
Article 23: obligations of importers
praxikon:eu:ai-act:obligation:article-23-importer-obligations
Before placing a system on the market the importer verifies four things about the provider, and afterwards carries its own retention, information and notification package with a ten-year term.
Placed against the official source | value-chain
- ObligationApplicablev1.0.016 relations
Article 99, 100 and 101: the penalty structure per obligation
praxikon:eu:ai-act:obligation:article-99-101-penalties
The Regulation carries no single fine amount. For operators, three ceilings attach to different paragraphs of Article 99; in addition the Commission itself fines providers of general-purpose AI models under Article 101, the AI Office can fine in its own right since the 2026 amendment, and Union institutions and bodies face the separate amounts of Article 100. Which ceiling applies depends on which provision was infringed and on who enforces, and not on how serious the consequences are.
Placed against the official source | enforcement, prohibited-practices
- TemplateApplicablev1.0.07 relations
Full text of Article 111
praxikon:eu:ai-act:template:article-111-legal-text
The legal text on EUR-Lex: the base text in Regulation (EU) 2024/1689 and the replacement of paragraph 2 and the addition of paragraph 4 in Regulation (EU) 2026/1744. Reading only the base text means reading the 2024 version.
Hangs off: Article 111(2): legacy high-risk systems and the 2 August 2030 date
Editorially reviewed | high-risk, timeline
- Templatev1.0.03 relations
Full text of Article 23
praxikon:eu:ai-act:template:article-23-importer-obligations-legal-text
The full legal text in the public AI Act Explorer.
Hangs off: Article 23: obligations of importers
Editorially reviewed | template, value-chain
- TemplateApplicablev1.0.08 relations
Full text of Article 99, 100 and 101
praxikon:eu:ai-act:template:article-99-101-legal-text
The full legal text in the public AI Act Explorer. Note that the explorer shows the original 2024 text, so for paragraph 1, point (da) and paragraph 6a of Article 99 you also need Regulation (EU) 2026/1744, to which the second source link points.
Hangs off: Article 99, 100 and 101: the penalty structure per obligation
Editorially reviewed | enforcement, template
What this explorer does not do
- There is no article object. The article sits as a locator on the citations of an obligation, as free text. Filtering on the obligation is the same question, and the data does carry that.
- No object carries an Annex III domain or use case. A selection of the form "systems for this purpose" cannot be expressed here.
- A locator hangs on a statement in the data, not on a relation. The source next to a path is the source anchor of the object carrying the relation, not proof of that one connection.
- The split between duty holder and affected actor exists on obligations only. On every other type the actor list is still one undifferentiated list.
- The graph stores no inverse relations. The incoming direction is computed here over the same release and adds nothing to the data.
- Topics are free slugs, not a taxonomy with objects, labels or a hierarchy of their own.
The same selection as data
The explorer and the API read the same object against the same two time axes. What you see here can be fetched with the same parameters.