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
32 objects in this selection.
- ActionApplicablev1.0.04 relations
Appoint an authorised representative and record the mandate
praxikon:eu:ai-act:action:appoint-gpai-authorised-representative
Determine whether you are the provider of the model, appoint an authorised representative established in the Union by written mandate before placing the model on the market, and write out in that mandate the four tasks in paragraph 3, the access to the Annex XI documentation and the point of contact under paragraph 4.
Hangs off: Article 54: authorised representative of a provider of a GPAI model
Editorially reviewed | gpai, value-chain
- ActionApplicablev1.0.05 relations
Submit the testing plan, obtain approval and register the test
praxikon:eu:ai-act:action:article-60-testing-plan-and-authorisation
Draw up a real-world testing plan, submit it to the market surveillance authority, obtain approval, register the test with a Union-wide unique single identification number, and record the division of roles with your deployer.
Hangs off: Article 60: testing in real world conditions outside a sandbox
Editorially reviewed | innovation
- 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.06 relations
Enter your data in the EU database and keep it up to date
praxikon:eu:ai-act:action:enter-and-maintain-eu-database-data
Compile per system the data listed in Sections A and B of Annex VIII, or Section C where you are a public deployer, designate the natural person with the legal authority to register, and make sure the entry stays correct when the status, the Member States or the declaration of conformity change. Section C can only be completed after the provider has entered Section A, because point 3 asks for the URL of that entry.
Hangs off: Article 71: EU database for high-risk AI systems listed in Annex III
Editorially reviewed | conformity
- ActionUpcomingv1.0.04 relations
Make your conformity file deliverable on request
praxikon:eu:ai-act:action:prepare-authority-information-request
Map per high-risk system where each part of the file sits, which system version it belongs to, who assembles it, how long the logs are kept and in which language indicated by the Member State concerned you can supply it, so that a reasoned request becomes a delivery task rather than a search.
Hangs off: Article 21: cooperation with competent authorities
Editorially reviewed | high-risk-requirements
- ActionApplicablev1.0.07 relations
Register yourself and the system before it reaches the market or is put into service
praxikon:eu:ai-act:action:register-in-eu-database-before-market-entry
Determine per system which of the four Article 49 routes applies, the ordinary Annex III route, the Article 6(3) route, the secure section for law enforcement, migration, asylum and border control management, or the national route for point 2 of Annex III, and complete the registration before the system is placed on the market, put into service or used.
Hangs off: Article 49: registration in the EU database before the system reaches the market
Editorially reviewed | conformity, high-risk
- ActorIn forcev1.0.034 relations
Authorised representative
praxikon:eu:ai-act:actor:authorised-representative
The authorised representative is the party located in the Union that, on the basis of a written mandate, performs and carries out the obligations and procedures of the Regulation on behalf of a provider established outside the EU. The definition in Article 3(5) already applies today, so the role can be determined now. The appointment duty itself starts on 2 December 2027 for the standalone Annex III route and on 2 August 2028 for the embedded Annex I route. From those dates, a third-country provider may not place a high-risk AI system on the Union market without an appointed representative.
Editorially reviewed | value-chain
- ControlApplicablev1.0.07 relations
Release gate: no market entry without registration
praxikon:eu:ai-act:control:article-49-pre-market-registration-gate
The control that stops any Annex III system from being placed on the market, put into service or used before the registration is complete, with an explicit check on the Article 6(3) route and on the Article 26(8) question whether the provider entry is present in the database.
Hangs off: Article 49: registration in the EU database before the system reaches the market
Editorially reviewed | conformity, control, high-risk
- 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.05 relations
Currency check on the database entry
praxikon:eu:ai-act:control:eu-database-entry-currency
The control that ensures a change of status, Member States, certificate or declaration of conformity leads to an updated entry within a set period, and that a public deployer notices when the provider does not enter its Section A or enters it late, instead of the public page quietly lagging behind reality.
Hangs off: Article 71: EU database for high-risk AI systems listed in Annex III
Editorially reviewed | conformity, control
- ControlApplicablev1.0.04 relations
Periodic review and termination of the mandate
praxikon:eu:ai-act:control:gpai-mandate-review
The control that ensures the representative can actually reach the documentation, that the verification under paragraph 3(a) is repeated at a fixed moment, and that there is an agreed route for the termination under paragraph 5 with the immediate notification to the AI Office. Without such a moment a mandate stays on paper while nobody tests it.
Hangs off: Article 54: authorised representative of a provider of a GPAI model
Editorially reviewed | control, gpai
- DefinitionIn forcev1.0.03 relations
Authorised representative
praxikon:eu:ai-act:definition:definitie-gemachtigde
The European point of contact for a provider from outside the Union, valid only on the basis of a written mandate.
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
Widespread infringement
praxikon:eu:ai-act:definition:definitie-wijdverbreide-inbreuk
An act or omission contrary to Union law protecting the interests of individuals that harms the collective interests of persons in at least two other Member States, or that, with common features, occurs concurrently and is committed by the same operator in at least three Member States.
Placed against the official source | definitions
- EvidenceApplicablev1.0.07 relations
Article 49 registration dossier
praxikon:eu:ai-act:evidence:article-49-registration-dossier
Per system: which Article 49 route was followed, the registration number, the date of registration, the name of the person who submitted it, the system version the entry relates to, and, for the secure section, a statement of which limited fields from Annex VIII and Annex IX were completed.
Hangs off: Article 49: registration in the EU database before the system reaches the market
Editorially reviewed | conformity, evidence, high-risk
- 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.05 relations
EU database registration file
praxikon:eu:ai-act:evidence:eu-database-entry-record
Per system: which Annex VIII data was entered, by which natural person with the legal authority to do so, on what date, in which version, when the entry was last checked against reality, and for a public deployer the URL of the entry made by the provider. This is also the file that shows the public entry and your internal documents say the same thing.
Hangs off: Article 71: EU database for high-risk AI systems listed in Annex III
Editorially reviewed | conformity, evidence
- EvidenceApplicablev1.0.04 relations
Mandate file of the authorised representative
praxikon:eu:ai-act:evidence:gpai-representative-mandate-file
The written mandate itself, in an official language of the institutions of the Union, together with the copy of the Annex XI technical documentation, the contact details of the provider, and the record of the verification under paragraph 3(a). The provider grants the mandate and supplies the documentation; the ten year retention after the placing on the market rests under paragraph 3(b) with the representative, which keeps the file at the disposal of the AI Office and national competent authorities.
Hangs off: Article 54: authorised representative of a provider of a GPAI model
Editorially reviewed | evidence, gpai
- 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.012 relations
Article 18: documentation keeping
praxikon:eu:ai-act:obligation:article-18-document-retention
The provider of a high-risk AI system keeps the technical documentation, the quality management system documentation, the changes approved by notified bodies and the decisions they issued, and the EU declaration of conformity at the disposal of the national competent authorities for a period ending ten years after the system has been placed on the market or put into service.
Placed against the official source | high-risk-requirements
- 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.012 relations
Article 21: cooperation with competent authorities
praxikon:eu:ai-act:obligation:article-21-cooperation-with-authorities
Upon a reasoned request by a competent authority, the provider of a high-risk AI system provides all the information and documentation necessary to demonstrate conformity with the requirements of Chapter III, Section 2, in a language which can be easily understood by the authority in one of the official languages of the institutions of the Union as indicated by the Member State concerned. Upon the same request the provider also gives, as applicable, access to the automatically generated logs, to the extent those logs are under its control.
Placed against the official source | high-risk-requirements
- ObligationApplicablev1.0.017 relations
Article 49: registration in the EU database before the system reaches the market
praxikon:eu:ai-act:obligation:article-49-registration
The provider of a high-risk AI system listed in Annex III, or where applicable its authorised representative, registers itself and that system in the EU database before it is placed on the market or put into service. The same duty applies to the provider that concludes under Article 6(3) that its Annex III system is precisely not high-risk: that provider too registers itself and that system. The deployer that is a public authority or a Union body, or that acts on behalf of such an authority, registers itself, selects the system and registers its use. For the areas of law enforcement, migration, asylum and border control management the registration goes into a secure non-public section with fewer fields, to which only the Commission and the national authorities referred to in Article 74(8) have access. For the systems in point 2 of Annex III registration does not run through the EU database but at national level.
Placed against the official source | conformity, high-risk
- ObligationApplicablev1.0.015 relations
Article 54: authorised representative of a provider of a GPAI model
praxikon:eu:ai-act:obligation:article-54-gpai-authorised-representative
A provider established in a third country appoints, by written mandate, an authorised representative established in the Union before placing a general-purpose AI model on the Union market. The representative performs the tasks the mandate assigns to it and provides a copy of that mandate to the AI Office upon request. The mandate empowers it at least to verify the documentation, keep a copy available for ten years, provide information and cooperate, and appoints it as the point of contact in addition to or instead of the provider.
Hangs off: Article 53: GPAI model providers, Article 55: GPAI models with systemic risk
Placed against the official source | gpai, value-chain
- ObligationUpcomingv1.0.015 relations
Article 71: EU database for high-risk AI systems listed in Annex III
praxikon:eu:ai-act:obligation:article-71-eu-database
The provider or, where applicable, the authorised representative enters the data listed in Sections A and B of Annex VIII into the EU database; the deployer who is, or who acts on behalf of, a public authority, agency or body enters the data listed in Section C. Information registered in accordance with Article 49 is publicly available in a user-friendly manner and machine-readable, except for the secure section covering law enforcement, migration, asylum and border control management and the registration of testing in real world conditions. Setting up and maintaining the database itself is a task of the Commission and not a duty of yours.
Placed against the official source | conformity, high-risk
- 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
- StandardGuidancev1.0.03 relations
prEN 18285: conformity assessment framework for AI systems
praxikon:eu:ai-act:standard:standard-pren-18285-conformity-assessment-framework
The draft European standard operationalising the conformity assessment procedure of Article 43 and Annex VII.
Hangs off: Articles 43-49: conformity assessment, CE and registration
Placed against the official source | standards
- 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
- TemplateUpcomingv1.0.07 relations
Full text of Article 49
praxikon:eu:ai-act:template:article-49-legal-text
The full legal text in the public AI Act Explorer.
Hangs off: Article 49: registration in the EU database before the system reaches the market
Editorially reviewed | conformity, high-risk, template
- TemplateApplicablev1.0.04 relations
Full text of Article 54
praxikon:eu:ai-act:template:article-54-legal-text
The full legal text in the public AI Act Explorer.
Hangs off: Article 54: authorised representative of a provider of a GPAI model
Editorially reviewed | gpai, template
- TemplateUpcomingv1.0.05 relations
Full text of Article 71
praxikon:eu:ai-act:template:article-71-legal-text
The full legal text in the public AI Act Explorer.
Hangs off: Article 71: EU database for high-risk AI systems listed in Annex III
Editorially reviewed | conformity, template
- 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.