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
147 objects in this selection.
- Actionv1.0.02 relations
Classify the use case and document the outcome
praxikon:eu:ai-act:action:annex-iii-classify
Assess Article 5, Article 6 and Annex III in that order and document purpose, context and any Article 6(3) exception.
Editorially reviewed | high-risk
- ActionApplicablev1.0.03 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
- Actionv1.0.02 relations
Set up data governance per dataset
praxikon:eu:ai-act:action:article-10-data-governance-act
Assess origin, representativeness, errors and completeness and examine possible bias with appropriate mitigation.
Editorially reviewed | high-risk-requirements
- Actionv1.0.01 relations
Build the technical file per Annex IV
praxikon:eu:ai-act:action:article-11-technical-documentation-act
Document system description, development process, data, oversight measures, performance and risk management before market placement.
Editorially reviewed | high-risk-requirements
- Actionv1.0.02 relations
Design logging into the system
praxikon:eu:ai-act:action:article-12-logging-act
Ensure the system automatically records events relevant to risk identification and post-market monitoring.
Editorially reviewed | high-risk-requirements
- Actionv1.0.02 relations
Provide complete instructions for use
praxikon:eu:ai-act:action:article-13-instructions-act
Describe capabilities, limitations, accuracy, oversight measures and expected lifetime in comprehensible form.
Editorially reviewed | high-risk-requirements
- Actionv1.0.02 relations
Design and assign effective human oversight
praxikon:eu:ai-act:action:article-14-human-oversight-act
Determine oversight measures per system, appoint competent persons and give them the mandate to intervene or stop.
Editorially reviewed | high-risk-requirements
- Actionv1.0.01 relations
Set and test performance and security levels
praxikon:eu:ai-act:action:article-15-accuracy-robustness-act
Determine appropriate accuracy, test robustness against errors and misuse, and take AI-specific security measures.
Editorially reviewed | high-risk-requirements
- Actionv1.0.01 relations
Set up an AI quality management system
praxikon:eu:ai-act:action:article-17-quality-management-act
Describe strategies, procedures and responsibilities for compliance, from design and data to post-market monitoring.
Editorially reviewed | high-risk-requirements
- Actionv1.0.04 relations
Take role- and context-specific AI literacy measures
praxikon:eu:ai-act:action:article-4-measures
Determine for each role, system and context which combination of instruction, guidance, practice or training is appropriate.
Hangs off: Article 4: AI literacy
Editorially reviewed | ai-literacy
- Actionv1.0.04 relations
Screen every use case against Article 5 first
praxikon:eu:ai-act:action:article-5-screen
Before procurement, build or deployment, check whether the use case falls under a prohibited practice and stop or redesign early rather than after the fact.
Hangs off: Article 5: prohibited practices
Editorially reviewed | prohibited-practices
- Actionv1.0.02 relations
Implement the applicable disclosure, marking or label
praxikon:eu:ai-act:action:article-50-disclosure
First determine which paragraph of Article 50 applies, then implement the specific transparency measure.
Editorially reviewed | transparency
- Actionv1.0.03 relations
Perform model evaluations and risk mitigation
praxikon:eu:ai-act:action:article-55-gpai-systemic-risk-act
Evaluate the model including adversarial testing, assess and mitigate systemic risks, report serious incidents and secure the model.
Hangs off: Article 55: GPAI models with systemic risk
Editorially reviewed | gpai-systemic-risk
- Actionv1.0.02 relations
Draw up a post-market monitoring plan
praxikon:eu:ai-act:action:article-72-post-market-monitoring-act
Systematically collect and analyse real-world data on the system’s performance and compliance throughout its lifetime.
Editorially reviewed | post-market
- Actionv1.0.02 relations
Set up an incident process with reporting routes
praxikon:eu:ai-act:action:article-73-incident-reporting-act
Define what a serious incident is, assign the reporting route to the supervisor and rehearse the process.
Editorially reviewed | post-market
- Actionv1.0.01 relations
Set up an iterative risk management process
praxikon:eu:ai-act:action:article-9-risk-management-act
Identify and analyse known and reasonably foreseeable risks, evaluate them and take measures, repeating the cycle on every change.
Editorially reviewed | high-risk-requirements
- Actionv1.0.02 relations
Complete the conformity route before market placement
praxikon:eu:ai-act:action:conformity-ce-registration-act
Select the correct assessment procedure, draw up the EU declaration of conformity, affix the CE marking and register in the EU database.
Editorially reviewed | conformity
- ActionEditorialv1.0.04 relations
Take and record the decision whether you adhere to a code of practice
praxikon:eu:ai-act:action:decide-and-record-gpai-code-adherence
Determine per general-purpose AI model whether you adhere to a code of practice, to which version and which chapter, whether under paragraph 7 the obligations in Article 53 suffice for you, and which elaboration of your own you apply for the issues in paragraph 2 where you do not join.
Hangs off: Article 56: codes of practice for general-purpose AI models
Editorially reviewed | governance, gpai, gpai-systemic-risk
Assess process, duration, affected persons, risks, oversight, mitigation and complaint mechanisms and notify results where required.
Editorially reviewed | fundamental-rights, high-risk
- Actionv1.0.03 relations
Maintain GPAI documentation and transparency information
praxikon:eu:ai-act:action:gpai-document
Maintain technical documentation, information for downstream providers, a copyright policy and a public summary of training content.
Hangs off: Article 53: GPAI model providers
Editorially reviewed | gpai
- ActionEditorialv1.0.05 relations
Mark and register what you submit to an authority or body
praxikon:eu:ai-act:action:mark-confidential-material-on-submission
State on every submission which part is confidential business information, trade secret or source code, keep track of what was handed to whom on what date, and on a further request ask about the necessity and the purpose within the meaning of Article 78(2).
Hangs off: Article 78: confidentiality of what you submit to an authority
Editorially reviewed | enforcement, governance
- ActionApplicablev1.0.03 relations
Notify the Commission within two weeks
praxikon:eu:ai-act:action:notify-systemic-risk-threshold
Notify the model as soon as it meets the condition in Article 51(1), point (a), or as soon as it becomes known that it will, with the information necessary to demonstrate that the requirement has been met, and with any substantiation that the model does not present systemic risks after all.
Hangs off: Article 52: notification of a GPAI model with systemic risk
Editorially reviewed | gpai-systemic-risk
- ActionApplicablev1.0.03 relations
Request reassessment after a designation
praxikon:eu:ai-act:action:request-systemic-risk-reassessment
If your model has been designated under Article 52(4), you may request reassessment by reasoned request. The request must contain objective, detailed and new reasons that have arisen since the designation decision, and may be made at the earliest six months after that decision; where the designation is maintained, a further six months apply.
Hangs off: Article 52: notification of a GPAI model with systemic risk
Editorially reviewed | gpai-systemic-risk
- Actionv1.0.02 relations
Assess the value-chain role per system and change
praxikon:eu:ai-act:action:value-chain-representative-act
On white-labelling, substantial modification or purpose change, assess whether your organisation becomes the provider, and arrange the representative for non-EU supply.
Editorially reviewed | value-chain
- ActionEditorialv1.0.03 relations
Check the standing and independence of your notified body
praxikon:eu:ai-act:action:verify-notified-body-standing
At the moment of choice and periodically thereafter, verify whether the body appears in the Commission public list, for which activities and system types it is notified, whether its designation has been restricted or suspended, and whether the independence of Article 31(4) and (5) holds; also ask which tasks are subcontracted and give your agreement under Article 33(3) in writing.
Hangs off: Articles 28 to 39: notifying authorities and notified bodies
Editorially reviewed | conformity, governance
The Commission office that supervises providers of general-purpose AI models. AI Office enforcement is active since 2 August 2026.
Editorially reviewed | enforcement, governance, gpai
- Actorv1.0.05 relations
Credit or insurance deployer
praxikon:eu:ai-act:actor:credit-or-insurance-deployer
A deployer of the relevant creditworthiness or life and health insurance systems in Annex III point 5(b) or 5(c).
Editorially reviewed | fundamental-rights, high-risk
An organisation using an AI system under its authority, excluding personal non-professional use.
Editorially reviewed | governance
A party that places a general-purpose AI model on the Union market.
Editorially reviewed | gpai
- Actorv1.0.02 relations
Market surveillance authority
praxikon:eu:ai-act:actor:market-surveillance-authority
The national authority that supervises compliance with the Regulation and receives serious incident and risk notifications. Which body fills this role per Member State is not recorded in the graph.
Editorially reviewed | enforcement, governance
A party that develops or has an AI system developed and places it on the market under its own name.
Editorially reviewed | governance
A deployer that is a body governed by public law.
Editorially reviewed | fundamental-rights
- Actorv1.0.06 relations
Private provider of public services
praxikon:eu:ai-act:actor:public-service-provider
A private deployer providing public services.
Editorially reviewed | fundamental-rights
- ChangeApplicablev1.0.04 relations
The AI Act enters into force
praxikon:eu:ai-act:change:2024-08-01-entry-into-force
The regulation entered into force on 1 August 2024, after which the obligations followed in phases.
Hangs off: Article 4: AI literacy, Article 5: prohibited practices
Placed against the official source | timeline
- ChangeApplicablev1.0.04 relations
Prohibited practices and AI literacy apply
praxikon:eu:ai-act:change:2025-02-02-prohibitions-and-literacy-applicable
Since 2 February 2025 the Article 5 prohibition and the Article 4 AI literacy duty apply.
Hangs off: Article 4: AI literacy, Article 5: prohibited practices
Placed against the official source | ai-literacy, timeline
- ChangeGuidancev1.0.02 relations
General-Purpose AI Code of Practice published
praxikon:eu:ai-act:change:2025-07-10-gpai-code-of-practice
The voluntary code of practice gives GPAI model providers a route to demonstrate compliance.
Hangs off: Article 53: GPAI model providers
Placed against the official source | gpai
- ChangeGuidancev1.0.03 relations
Guidelines on the scope of the GPAI obligations
praxikon:eu:ai-act:change:2025-07-18-gpai-guidelines
The Commission explains when someone becomes the provider of a GPAI model, including through fine-tuning.
Hangs off: Article 53: GPAI model providers, Article 55: GPAI models with systemic risk
Placed against the official source | gpai
- ChangeGuidancev1.0.03 relations
Guidelines on the definition of an AI system
praxikon:eu:ai-act:change:2025-07-29-ai-system-definition-guidelines
The Commission draws the line between software that does and does not fall under the regulation.
Hangs off: Article 4: AI literacy
Placed against the official source | scope
- ChangeGuidancev1.0.03 relations
Guidelines on prohibited AI practices
praxikon:eu:ai-act:change:2025-07-29-prohibited-practices-guidelines
Worked examples for each Article 5 prohibition, with the line between permitted and prohibited.
Hangs off: Article 5: prohibited practices
Placed against the official source | prohibited
- ChangeApplicablev1.0.03 relations
GPAI model obligations apply
praxikon:eu:ai-act:change:2025-08-02-gpai-obligations-applicable
Since 2 August 2025 the obligations for providers of general-purpose AI models apply.
Hangs off: Article 53: GPAI model providers, Article 55: GPAI models with systemic risk
Placed against the official source | gpai, timeline
- ChangeUpcomingv1.0.04 relations
Legacy GPAI models must comply
praxikon:eu:ai-act:change:2027-08-02-legacy-gpai-models-comply
Models placed on the market before 2 August 2025 have until 2 August 2027.
Hangs off: Article 53: GPAI model providers, Article 55: GPAI models with systemic risk
Placed against the official source | gpai, timeline
- Controlv1.0.02 relations
Reclassification on purpose or context change
praxikon:eu:ai-act:control:annex-iii-change-trigger
Reopen classification when intended purpose, use context or system functionality changes materially.
Editorially reviewed | control, high-risk
- Controlv1.0.02 relations
Data check before retraining
praxikon:eu:ai-act:control:article-10-data-governance-control
Repeat the data quality assessment before every retraining or dataset change.
Editorially reviewed | control, high-risk-requirements
- Controlv1.0.01 relations
Documentation update on every release
praxikon:eu:ai-act:control:article-11-technical-documentation-control
Update the file before every release and retain earlier versions traceably.
Editorially reviewed | control, high-risk-requirements
Periodically verify that logging works, is complete and is retained according to the regime.
Editorially reviewed | control, high-risk-requirements
- Controlv1.0.02 relations
Instructions check at deployment
praxikon:eu:ai-act:control:article-13-instructions-control
At every deployment and update, verify instructions are present, current and internally translated.
Editorially reviewed | control, high-risk-requirements
- Controlv1.0.02 relations
Oversight test before go-live
praxikon:eu:ai-act:control:article-14-human-oversight-control
Before go-live, test that intervening, stopping and disregarding output actually works and is assigned.
Editorially reviewed | control, high-risk-requirements
- Controlv1.0.01 relations
Performance monitoring in use
praxikon:eu:ai-act:control:article-15-accuracy-robustness-control
Monitor whether the system stays within declared levels in production and escalate on deviation.
Editorially reviewed | control, high-risk-requirements
- Controlv1.0.01 relations
Internal audit cycle
praxikon:eu:ai-act:control:article-17-quality-management-control
Periodically audit whether practice follows the described system and record deviations and improvements.
Editorially reviewed | control, high-risk-requirements
- Controlv1.0.04 relations
Periodic role and context review
praxikon:eu:ai-act:control:article-4-periodic-review
Check when systems, roles or risks change whether the selected measures remain appropriate.
Hangs off: Article 4: AI literacy
Editorially reviewed | ai-literacy, control
- Controlv1.0.04 relations
Article 5 gate at intake and change
praxikon:eu:ai-act:control:article-5-intake-gate
Repeat the screening for every new system, procurement and material change of purpose or context; an earlier clearance does not cover a new use.
Hangs off: Article 5: prohibited practices
Editorially reviewed | control, prohibited-practices
- Controlv1.0.02 relations
Pre-release transparency check
praxikon:eu:ai-act:control:article-50-release-check
Before release, test that the applicable disclosure, marking or label is timely, clear and technically effective.
Editorially reviewed | control, transparency
- Controlv1.0.03 relations
Compute threshold monitoring
praxikon:eu:ai-act:control:article-55-gpai-systemic-risk-control
Monitor cumulative training compute and notify the Commission when the threshold is reached.
Hangs off: Article 55: GPAI models with systemic risk
Editorially reviewed | control, gpai-systemic-risk
- ControlEditorialv1.0.04 relations
Review moment on your reliance on a code of practice
praxikon:eu:ai-act:control:article-56-code-commitment-review
The control that periodically rechecks a reliance on a code of practice: does the version you rely on still stand, has the code been reviewed or adapted under paragraph 8, has the Commission published its assessment of adequacy under paragraph 6 as replaced by Regulation (EU) 2026/1744, and has the Commission laid down common rules under paragraph 9.
Hangs off: Article 56: codes of practice for general-purpose AI models
Editorially reviewed | control, governance, gpai, gpai-systemic-risk
- Controlv1.0.02 relations
Signal-to-action loop
praxikon:eu:ai-act:control:article-72-post-market-monitoring-control
Ensure real-world signals (deviations, complaints, incidents) demonstrably lead to analysis and, where needed, measures.
Editorially reviewed | control, post-market
- Controlv1.0.02 relations
Incident drill and deadline watch
praxikon:eu:ai-act:control:article-73-incident-reporting-control
Periodically test whether an incident can be reported within the legal deadlines, including the deployer-to-provider chain.
Editorially reviewed | control, post-market
- ControlEditorialv1.0.05 relations
Review before handing over source code or trade secrets
praxikon:eu:ai-act:control:article-78-disclosure-review
The control that sends a submission touching source code, training methodology or trade secrets through a fixed review: is the request reasoned, what purpose was stated, which part is strictly necessary, and who inside the organisation signs off on it.
Hangs off: Article 78: confidentiality of what you submit to an authority
Editorially reviewed | control, enforcement, governance
- Controlv1.0.01 relations
Reassessment on every material change
praxikon:eu:ai-act:control:article-9-risk-management-control
Reopen the risk management process on changes in purpose, data, model or use context and before every release.
Editorially reviewed | control, high-risk-requirements
- Controlv1.0.02 relations
Reassessment on substantial modification
praxikon:eu:ai-act:control:conformity-ce-registration-control
Rerun the conformity route whenever the system is substantially modified.
Editorially reviewed | conformity, control
- Controlv1.0.03 relations
Pre-deployment FRIA go/no-go
praxikon:eu:ai-act:control:fria-pre-deployment-gate
Block deployment until applicability, assessment, mitigation and notification have been completed.
Editorially reviewed | control, fundamental-rights
- Controlv1.0.03 relations
GPAI documentation change control
praxikon:eu:ai-act:control:gpai-documentation-change-control
Update documentation and downstream information when the model, capabilities or risks change.
Hangs off: Article 53: GPAI model providers
Editorially reviewed | control, gpai
- ControlApplicablev1.0.03 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
- ControlEditorialv1.0.03 relations
Control on the continuity of your conformity assessment
praxikon:eu:ai-act:control:notified-body-continuity-review
The control that absorbs the loss of a notified body: a fixed periodic check of the public list, a contractual reporting duty mirroring the ten days of Article 36(5), a named alternative body for your type of system, and a handover procedure that stays within the nine months of Article 36(3) and (9).
Hangs off: Articles 28 to 39: notifying authorities and notified bodies
Editorially reviewed | conformity, control, governance
- ControlApplicablev1.0.03 relations
Deadline tracking of the notification
praxikon:eu:ai-act:control:systemic-risk-notification-deadline
The control that ensures the signal from the training pipeline reaches an identifiable owner and that the notification goes out within two weeks. Its trigger point is the allocation of compute and not the end of the run, because recital 111 also counts pre-training, synthetic data and fine-tuning and recital 112 assumes the provider knows the outcome before then. It sits alongside the monitoring of compute itself: that measures the threshold, this guards the clock that starts afterwards.
Hangs off: Article 52: notification of a GPAI model with systemic risk
Editorially reviewed | gpai-systemic-risk
- Controlv1.0.02 relations
Role reassessment on every change
praxikon:eu:ai-act:control:value-chain-representative-control
Repeat the role assessment on every rebranding, modification or new use of an existing system.
Editorially reviewed | control, value-chain
- Evidencev1.0.02 relations
Article 6 and Annex III classification record
praxikon:eu:ai-act:evidence:annex-iii-classification-record
Traceable rationale covering intended purpose, Annex III category, Article 6(3) assessment and registration decision.
Editorially reviewed | evidence, high-risk
- Evidencev1.0.02 relations
Data governance file
praxikon:eu:ai-act:evidence:article-10-data-governance-record
Record per dataset of origin, choices, assumptions, bias examination and mitigations.
Editorially reviewed | evidence, high-risk-requirements
- Evidencev1.0.01 relations
Technical file (Annex IV)
praxikon:eu:ai-act:evidence:article-11-technical-documentation-record
Technical documentation kept current per system version, ready for a supervisor’s request.
Editorially reviewed | evidence, high-risk-requirements
- Evidencev1.0.02 relations
Logs and retention regime
praxikon:eu:ai-act:evidence:article-12-logging-record
Log files with a retention period appropriate to the purpose and at least six months for deployers (Articles 19 and 26).
Editorially reviewed | evidence, high-risk-requirements
- Evidencev1.0.02 relations
Instructions and interpretation file
praxikon:eu:ai-act:evidence:article-13-instructions-record
The received instructions for use plus their internal translation into work instructions per role.
Editorially reviewed | evidence, high-risk-requirements
- Evidencev1.0.02 relations
Oversight file per system
praxikon:eu:ai-act:evidence:article-14-human-oversight-record
Record of oversight measures, appointed persons, their training and the moments of intervention.
Editorially reviewed | evidence, high-risk-requirements
- Evidencev1.0.01 relations
Performance and security file
praxikon:eu:ai-act:evidence:article-15-accuracy-robustness-record
Declared accuracy levels, test results, and measures against data poisoning and adversarial attacks among others.
Editorially reviewed | evidence, high-risk-requirements
- Evidencev1.0.01 relations
QMS documentation
praxikon:eu:ai-act:evidence:article-17-quality-management-record
The documented quality system with procedures, role assignment and references to the underlying files.
Editorially reviewed | evidence, high-risk-requirements
- Evidencev1.0.04 relations
AI literacy measures record
praxikon:eu:ai-act:evidence:article-4-measures-record
Versioned record of roles, context, measures, participation or instruction and review moments.
Hangs off: Article 4: AI literacy
Editorially reviewed | ai-literacy, evidence
- Evidencev1.0.04 relations
Article 5 screening record
praxikon:eu:ai-act:evidence:article-5-screening-record
A record per system that the Article 5 screening was performed, with outcome and reasoning. The conclusion "no prohibited practice" is evidence too.
Hangs off: Article 5: prohibited practices
Editorially reviewed | evidence, prohibited-practices
- Evidencev1.0.02 relations
Transparency implementation record
praxikon:eu:ai-act:evidence:article-50-implementation-record
Record of scenario, actor, disclosure or marking, technical implementation, test and owner.
Editorially reviewed | evidence, transparency
- Evidencev1.0.03 relations
Systemic-risk file
praxikon:eu:ai-act:evidence:article-55-gpai-systemic-risk-record
Evaluation results, risk assessments, mitigations, incident reports and security measures per model version.
Hangs off: Article 55: GPAI models with systemic risk
Editorially reviewed | evidence, gpai-systemic-risk
- EvidenceEditorialv1.0.04 relations
Record of the decision on a code of practice
praxikon:eu:ai-act:evidence:article-56-code-adherence-decision-record
Per model: the decision whether or not to adhere to a code of practice, the version and chapter it relates to, the date and the authorised signatory, whether adherence was limited under paragraph 7 to the obligations in Article 53, and, where the decision is negative, the elaboration of your own for the issues in paragraph 2.
Hangs off: Article 56: codes of practice for general-purpose AI models
Editorially reviewed | evidence, governance, gpai, gpai-systemic-risk
- Evidencev1.0.02 relations
Monitoring plan and reports
praxikon:eu:ai-act:evidence:article-72-post-market-monitoring-record
The plan as part of the technical documentation plus the periodic analyses and follow-up actions.
Editorially reviewed | evidence, post-market
- Evidencev1.0.02 relations
Incident register and reports
praxikon:eu:ai-act:evidence:article-73-incident-reporting-record
Record of incidents, analyses, reports to supervisors and corrective measures.
Editorially reviewed | evidence, post-market
- EvidenceEditorialv1.0.05 relations
Register of submissions to authorities
praxikon:eu:ai-act:evidence:article-78-submission-register
Per submission: which system, which document, which version, to which recipient, on what date, which part was marked confidential, and which purpose the recipient stated.
Hangs off: Article 78: confidentiality of what you submit to an authority
Editorially reviewed | enforcement, evidence, governance
- Evidencev1.0.01 relations
Risk management file
praxikon:eu:ai-act:evidence:article-9-risk-management-record
Versioned record of risk analyses, chosen measures, residual risks and test results per system version.
Editorially reviewed | evidence, high-risk-requirements
- Evidencev1.0.02 relations
Conformity file
praxikon:eu:ai-act:evidence:conformity-ce-registration-record
The assessment, EU declaration of conformity, CE marking and registration proof, per system version.
Editorially reviewed | conformity, evidence
Dated impact assessment, measures, residual risks and, where required, notification to the market surveillance authority.
Editorially reviewed | evidence, fundamental-rights
Current technical documentation, downstream information, copyright policy and public training summary.
Hangs off: Article 53: GPAI model providers
Editorially reviewed | evidence, gpai
- EvidenceApplicablev1.0.03 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
- EvidenceEditorialv1.0.03 relations
File on the chosen notified body
praxikon:eu:ai-act:evidence:notified-body-standing-record
Per body: identification number, Member State of establishment, the conformity assessment activities and system types for which it is notified, the date of each check against the public list, the outcome of the independence test, the subcontracted tasks with your written agreement, and every notice of a change to its designation.
Hangs off: Articles 28 to 39: notifying authorities and notified bodies
Editorially reviewed | conformity, evidence, governance
- EvidenceApplicablev1.0.03 relations
Systemic-risk notification file
praxikon:eu:ai-act:evidence:systemic-risk-notification-file
Per model version: the measured and planned training compute with the scope of recital 111, so including pre-training, synthetic data generation and fine-tuning, the moment the threshold was reached or foreseen, the notification sent with its supporting information, any arguments under paragraph 2, any reassessment request under paragraph 5, and the response or designation decision of the Commission.
Hangs off: Article 52: notification of a GPAI model with systemic risk
Editorially reviewed | gpai-systemic-risk
- Evidencev1.0.02 relations
Value-chain file
praxikon:eu:ai-act:evidence:value-chain-representative-record
Record per system of role, contractual arrangements on information and cooperation, and the appointment of a representative where required.
Editorially reviewed | evidence, value-chain
- ExampleEditorialv1.0.03 relations
Facial recognition at access control: the guard behind the camera counts too
praxikon:eu:ai-act:example:example-artikel-4-gezichtsherkenning-toegangscontrole
An organisation secures the entrances to its buildings with facial recognition and uses that biometric access control to register visitors as well. When the system returns no match, a security officer reviews the camera images and decides personally whether someone may enter. The question is whose measures have to reach that officer: those of the supplier of the model, those of the department that deploys the system, or both.
Hangs off: Article 4: AI literacy
Placed against the official source | examples
- ExampleEditorialv1.0.03 relations
Police using AI in investigations: context sets how deep the training goes
praxikon:eu:ai-act:example:example-artikel-4-politie-opsporingsanalyse
A police force uses AI to search large volumes of investigation files and surface connections a detective would otherwise miss. The outputs feed into the choice of which suspect is pursued further and end up in documents that enter the criminal process. The question is whether one and the same basic instruction is enough for the analyst operating the model and for the detective who acts on its output.
Hangs off: Article 4: AI literacy
Placed against the official source | examples
- ExampleEditorialv1.0.02 relations
Newsroom with generative AI: do freelancers count within your measures?
praxikon:eu:ai-act:example:example-artikel-4-redactie-generatieve-content
A newsroom uses generative AI to prepare summaries, headlines and imagery, after which an editor finishes the piece and the desk decides to publish. Part of that work sits with freelancers, and an outside agency produces marketing content with the same tools. The question is whether your AI literacy measures must reach those freelancers and that agency, or only the people on the payroll.
Hangs off: Article 4: AI literacy
Placed against the official source | examples
- ExampleEditorialv1.0.02 relations
AI chat in recruitment and selection: what the applicant must be told
praxikon:eu:ai-act:example:example-artikel-50-ai-chat-sollicitanten
A recruiter deploys an AI chat that puts candidates through a first screening conversation after they respond to a job posting, and adds their answers to their CV. The chat introduces itself with a first name and writes in a casual conversational tone. The question is whether these applicants reasonably realise that they are talking to an AI system.
Placed against the official source | examples
- ExampleEditorialv1.0.02 relations
Performance scoring for staff goes wrong: report or not
praxikon:eu:ai-act:example:example-beoordelingssysteem-personeel-incidentmelding
An employer uses an AI system that scores employee performance and lets that score weigh in promotion and dismissal. After a change to the model it turns out that a group of staff was scored too low for months, and decisions have already been taken on those scores. HR wonders whether this is a serious incident and who would have to report it.
Placed against the official source | examples
- ExampleEditorialv1.0.02 relations
Serious incident on the production line: who reports and within what deadline
praxikon:eu:ai-act:example:example-ernstig-incident-productielijn-meldtermijn
A manufacturer supplies an AI system that runs as a safety component in a machine on the production line and at the same time drives quality control. At a customer's factory an operator is seriously injured after the machine failed to stop on an anomaly. The question is who reports, to whom, and which clock is already running at that moment.
Placed against the official source | examples
- ExampleEditorialv1.0.02 relations
Awarding social assistance in a municipality: the FRIA and the notification
praxikon:eu:ai-act:example:example-fria-bijstandsuitkering-gemeente
A municipality wants to deploy an AI system that sorts applications for social assistance benefits and indicates which files merit extra scrutiny before a case worker decides. The application is already listed in the public algorithm register. The question is what has to be in place before the first citizen passes through this system.
Placed against the official source | examples
- ExampleEditorialv1.0.02 relations
Recidivism scoring in police work: when the assessment must be redone
praxikon:eu:ai-act:example:example-fria-recidiverisico-politie
A police service deploys an AI system that estimates the recidivism risk of a suspect, as an aid to the judgements later made by the prosecution service and the court. The model is subsequently retrained on newer investigative data and use is extended to a second region. The question is whether the assessment made for first use remains adequate.
Placed against the official source | examples
- ExampleEditorialv1.0.02 relations
Selection at student admission: a DPIA is not yet a FRIA
praxikon:eu:ai-act:example:example-fria-selectie-inschrijving-hogeschool
A university of applied sciences has an AI system rank applications for a vocational programme, using the exam results of earlier students to calibrate that ranking. A data protection impact assessment already exists for this processing. The question the school asks is whether that also covers the fundamental rights side of admission.
Placed against the official source | examples
- ExampleEditorialv1.0.01 relations
Logging in admission and assessment: what the institution keeps in its own hands
praxikon:eu:ai-act:example:example-logging-hogeschool-aanmelding-toetsing
A university of applied sciences uses a purchased AI system that ranks student admissions and also raises flags during digital assessment. The logs sit in the supplier environment, which hands them over on request. The teaching organisation wonders whether that settles the matter or whether the school retains a duty of its own.
Placed against the official source | examples
- ExampleEditorialv1.0.02 relations
Logging on the production line: which logs the manufacturer keeps and which the factory keeps
praxikon:eu:ai-act:example:example-logging-productielijn-veiligheidscomponent
A manufacturer supplies an AI system that runs as a safety component inside the machinery of a production line and also drives quality control. The factory operating the line keeps only the alerts visible in the local controller; the rest of the recording flows to the supplier environment. The question is who has to keep which logs when it later has to be reconstructed why the line was halted.
Placed against the official source | examples
- ExampleEditorialv1.0.01 relations
Logging in task allocation at work: evidence about the system or a file on the employee
praxikon:eu:ai-act:example:example-logging-taakverdeling-werkvloer
An employer deploys an AI system that handles task allocation among staff and summarises their performance for the performance review. HR wants to know what record of those outcomes has to be retained when an employee objects months later to a promotion decision.
Placed against the official source | examples
- ExampleEditorialv1.0.03 relations
Police fine-tuning a model for investigations: settle the role question first
praxikon:eu:ai-act:example:example-politie-model-bijtrainen-opsporing
A police service fine-tunes an open general-purpose model on its own files from ongoing criminal investigations, so that detectives can see links between suspects and cases sooner. The fine-tuned model stays inside the service and is not made available to anyone else. The question is whether the service thereby becomes a provider of a general-purpose AI model itself, and so falls under Article 53.
Hangs off: Article 53: GPAI model providers
Placed against the official source | examples
- ExampleEditorialv1.0.02 relations
Assessing staff: signals from the workplace flowing back to the provider
praxikon:eu:ai-act:example:example-post-market-monitoring-hr-beoordelingssysteem
A provider supplies a system that summarises employee performance data and supports HR in promotion decisions. After a year in use, departments turn out to apply it differently than intended, and managers factor the outputs into the performance review. The question is what the provider is supposed to know about that.
Placed against the official source | examples
- ExampleEditorialv1.0.02 relations
Proctoring during exams: which real-world data the institution reports back
praxikon:eu:ai-act:example:example-post-market-monitoring-proctoring-tentamens
A vendor offers proctoring software that flags possible cheating during exams. Several universities of applied sciences use the system, each with its own assessment formats and its own student populations. The vendor wants to know which real-world data it must keep collecting after roll-out, and from whom.
Placed against the official source | examples
- ExampleEditorialv1.0.02 relations
Safety component on the production line: the manufacturer keeps watching after delivery
praxikon:eu:ai-act:example:example-post-market-monitoring-veiligheidscomponent-productielijn
A manufacturer supplies an AI safety component that halts machinery on a production line as soon as someone comes too close to the robot. The component already falls under product legislation for machinery, and the manufacturer runs quality control and incident follow-up for it. The question is what Article 72 adds on top of that.
Placed against the official source | examples
- ExampleEditorialv1.0.02 relations
Proctoring during an exam overshoots: from signal to reporting duty
praxikon:eu:ai-act:example:example-proctoring-tentamen-incidentmelding
A university of applied sciences uses proctoring software during an online exam and finds that a group of students is systematically and wrongly flagged as suspicious, after which grades were withdrawn. Teaching staff and the examination board want to know whether this pattern is a serious incident and, if so, who has to report it and within what time.
Placed against the official source | examples
- ExampleEditorialv1.0.02 relations
Admission system at a higher education institution: who registers in the EU database
praxikon:eu:ai-act:example:example-toelating-hogeschool-registratie-eu-databank
A higher education institution procures an AI system that organises student applications and enrolment and produces an admission recommendation for each candidate in its vocational programmes. The supplier says it handles the conformity assessment itself and affixes the CE marking. What is left unresolved is whether the institution still has a step of its own to take before the system goes into use in its teaching.
Placed against the official source | examples
- ExampleEditorialv1.0.02 relations
Webshop builds its own consumer credit check: what belongs in the file
praxikon:eu:ai-act:example:example-webshop-kredietcheck-technisch-dossier
A non-food retail chain lets customers pay later in its webshop and decides at checkout whether a consumer qualifies. The team builds that assessment system in house, on top of a pre-trained model supplied by a vendor. The question is what has to be on record before the feature goes live, and who has to put it there.
Placed against the official source | examples
- ObligationApplicablev1.0.010 relations
Articles 28 to 39: notifying authorities and notified bodies
praxikon:eu:ai-act:obligation:article-28-39-notified-bodies
Section 4 of Chapter III governs who may carry out your conformity assessment and on what conditions that power continues to exist. Each Member State designates a notifying authority that assesses, designates, notifies and monitors conformity assessment bodies. A notified body is established under the national law of a Member State, has legal personality, and is independent of the provider, of any other operator with an economic interest and of the provider competitors; consultancy services in particular are ruled out. Subcontracting to a subcontractor or a subsidiary is allowed only with the agreement of the provider, and the body then retains full responsibility. In its work it avoids unnecessary burdens for providers and minimises administrative burdens and compliance costs for micro- and small enterprises, without giving up the required degree of rigour. Article 36 distinguishes the cases. Where it ceases its activities, the certificates remain valid under paragraph 3 for at most nine months, provided another notified body assumes responsibility in writing. Where its designation is suspended, restricted or withdrawn, it informs the providers concerned within ten days under paragraph 5; paragraph 8 sets continuity conditions there without that general nine-month limit, and paragraph 9 gives certificates a nine-month validity on withdrawal, with a conditional extension in periods of three months up to twelve months at most. A body from a third country can carry out these activities only where the Union has concluded an agreement with that country.
Placed against the official source | conformity, governance
- ObligationApplicablev1.0.016 relations
Article 4: AI literacy
praxikon:eu:ai-act:obligation:article-4-ai-literacy
Original duty to take measures for a sufficient level of AI literacy.
Placed against the official source | ai-literacy
- ObligationApplicablev1.0.015 relations
Article 5: prohibited practices
praxikon:eu:ai-act:obligation:article-5-prohibited-practices
The prohibition of AI practices carrying unacceptable risk, such as manipulation, social scoring and certain biometric applications.
Placed against the official source | prohibited-practices
- ObligationApplicablev1.0.014 relations
Article 52: notification of a GPAI model with systemic risk
praxikon:eu:ai-act:obligation:article-52-systemic-risk-classification
The provider of a general-purpose AI model that meets the condition in Article 51(1), point (a), notifies the Commission without delay and in any event within two weeks, with the information needed to demonstrate that the requirement has been met. With that notification the provider may present substantiated arguments that the model exceptionally does not present systemic risks after all.
Placed against the official source | gpai-systemic-risk
- ObligationApplicablev1.0.016 relations
Article 53: GPAI model providers
praxikon:eu:ai-act:obligation:article-53-gpai
Documentation, information, copyright and transparency duties for providers of general-purpose AI models.
Placed against the official source | gpai
- ObligationApplicablev1.0.013 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
- ObligationApplicablev1.0.015 relations
Article 55: GPAI models with systemic risk
praxikon:eu:ai-act:obligation:article-55-gpai-systemic-risk
Additional duties for the most capable general-purpose AI models, on top of Article 53.
Placed against the official source | gpai-systemic-risk
- ObligationApplicablev1.0.111 relations
Article 56: codes of practice for general-purpose AI models
praxikon:eu:ai-act:obligation:article-56-gpai-codes-of-practice
The AI Office encourages and facilitates the drawing up of codes of practice at Union level, and the AI Office and the Board see to it that those codes cover at least the obligations in Articles 53 and 55. Providers of general-purpose AI models and national competent authorities may be invited to participate in the drawing up; civil society organisations, industry, academia and other stakeholders may support the process. Until 27 July 2026 the Commission could approve a code of practice by implementing act and give it general validity within the Union; Article 1, point (21), of Regulation (EU) 2026/1744 replaced paragraph 6 and removed that power. Since then the Commission assesses whether the codes cover the obligations of Articles 53 and 55 and publishes that assessment. The codes were to be ready by 2 May 2025 at the latest; if no code existed by 2 August 2025, or if the AI Office deems one inadequate, the Commission may lay down common rules by implementing acts for the implementation of Articles 53 and 55. For you this is therefore not a separate duty but a route: a code is a voluntary instrument with which you can demonstrate compliance.
Placed against the official source | governance, gpai, gpai-systemic-risk
- ObligationApplicablev1.0.012 relations
Article 78: confidentiality of what you submit to an authority
praxikon:eu:ai-act:obligation:article-78-confidentiality
The Commission, the market surveillance authorities, the notified bodies and everyone involved in the application of the Regulation respect the confidentiality of what they obtain in carrying out their tasks, and in doing so expressly protect the intellectual property rights, the confidential business information and the trade secrets of a natural or legal person, including source code. They may request only data that is strictly necessary, must secure it, and must delete it as soon as it is no longer needed. For you this is therefore not a duty but a protection, with a limit: the exception in Article 5 of Directive (EU) 2016/943 remains, and the provision leaves the exchange of information and the dissemination of warnings between authorities untouched.
Placed against the official source | enforcement, governance
- Templatev1.0.02 relations
Annex III classification route
praxikon:eu:ai-act:template:annex-iii-classifier
Public classifier for the high-risk use cases in Annex III.
Editorially reviewed | high-risk, template
- Templatev1.0.02 relations
Full text of Article 10
praxikon:eu:ai-act:template:article-10-data-governance-legal-text
The full legal text in the public AI Act Explorer.
Editorially reviewed | high-risk-requirements, template
- Templatev1.0.01 relations
Full text of Article 11
praxikon:eu:ai-act:template:article-11-technical-documentation-legal-text
The full legal text in the public AI Act Explorer.
Editorially reviewed | high-risk-requirements, template
- Templatev1.0.02 relations
Full text of Article 12
praxikon:eu:ai-act:template:article-12-logging-legal-text
The full legal text in the public AI Act Explorer.
Editorially reviewed | high-risk-requirements, template
- Templatev1.0.02 relations
Full text of Article 13
praxikon:eu:ai-act:template:article-13-instructions-legal-text
The full legal text in the public AI Act Explorer.
Editorially reviewed | high-risk-requirements, template
- Templatev1.0.02 relations
Full text of Article 14
praxikon:eu:ai-act:template:article-14-human-oversight-legal-text
The full legal text in the public AI Act Explorer.
Editorially reviewed | high-risk-requirements, template
- Templatev1.0.01 relations
Full text of Article 15
praxikon:eu:ai-act:template:article-15-accuracy-robustness-legal-text
The full legal text in the public AI Act Explorer.
Editorially reviewed | high-risk-requirements, template
- Templatev1.0.01 relations
Full text of Article 16
praxikon:eu:ai-act:template:article-16-provider-obligations-legal-text
The full legal text in the public AI Act Explorer.
Editorially reviewed | high-risk-requirements, template
- Templatev1.0.01 relations
Full text of Article 17
praxikon:eu:ai-act:template:article-17-quality-management-legal-text
The full legal text in the public AI Act Explorer.
Editorially reviewed | high-risk-requirements, template
- Templatev1.0.00 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.
Editorially reviewed | template, value-chain
- Templatev1.0.00 relations
Full text of Article 24
praxikon:eu:ai-act:template:article-24-distributor-obligations-legal-text
The full legal text in the public AI Act Explorer.
Editorially reviewed | template, value-chain
- Templatev1.0.02 relations
Full text of Article 26
praxikon:eu:ai-act:template:article-26-deployer-obligations-legal-text
The full legal text in the public AI Act Explorer.
Editorially reviewed | high-risk-requirements, template
- TemplateApplicablev1.0.03 relations
Full text of Articles 28 to 39
praxikon:eu:ai-act:template:article-28-39-legal-text
The full legal text of Chapter III, Section 4, in the public AI Act Explorer.
Hangs off: Articles 28 to 39: notifying authorities and notified bodies
Editorially reviewed | conformity, governance, template
- Templatev1.0.04 relations
AI literacy measures plan
praxikon:eu:ai-act:template:article-4-measures-plan
Public route for structuring measures by role and context.
Hangs off: Article 4: AI literacy
Editorially reviewed | ai-literacy, template
The full legal text of the prohibited practices with all categories and exceptions, in the public AI Act Explorer.
Hangs off: Article 5: prohibited practices
Editorially reviewed | prohibited-practices, template
Public decision route for the distinct transparency obligations.
Editorially reviewed | template, transparency
- TemplateApplicablev1.0.03 relations
Full text of Article 52
praxikon:eu:ai-act:template:article-52-legal-text
The full legal text in the public AI Act Explorer.
Hangs off: Article 52: notification of a GPAI model with systemic risk
Editorially reviewed | gpai-systemic-risk
- TemplateApplicablev1.0.03 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
- Templatev1.0.03 relations
Full text of Article 55
praxikon:eu:ai-act:template:article-55-gpai-systemic-risk-legal-text
The full legal text in the public AI Act Explorer.
Hangs off: Article 55: GPAI models with systemic risk
Editorially reviewed | gpai-systemic-risk, template
- TemplateApplicablev1.0.04 relations
Full text of Article 56
praxikon:eu:ai-act:template:article-56-legal-text
The full legal text in the public AI Act Explorer.
Hangs off: Article 56: codes of practice for general-purpose AI models
Editorially reviewed | governance, gpai, gpai-systemic-risk, template
- Templatev1.0.03 relations
Full text of Article 57
praxikon:eu:ai-act:template:article-57-regulatory-sandboxes-legal-text
The full legal text in the public AI Act Explorer.
Editorially reviewed | innovation, template
- Templatev1.0.02 relations
Full text of Article 60
praxikon:eu:ai-act:template:article-60-real-world-testing-legal-text
The full legal text in the public AI Act Explorer.
Editorially reviewed | innovation, template
- Templatev1.0.02 relations
Full text of Article 72
praxikon:eu:ai-act:template:article-72-post-market-monitoring-legal-text
The full legal text in the public AI Act Explorer.
Editorially reviewed | post-market, template
- Templatev1.0.02 relations
Full text of Article 73
praxikon:eu:ai-act:template:article-73-incident-reporting-legal-text
The full legal text in the public AI Act Explorer.
Editorially reviewed | post-market, template
- TemplateApplicablev1.0.05 relations
Full text of Article 78
praxikon:eu:ai-act:template:article-78-legal-text
The full legal text in the public AI Act Explorer.
Hangs off: Article 78: confidentiality of what you submit to an authority
Editorially reviewed | enforcement, governance, template
- Templatev1.0.01 relations
Full text of Article 9
praxikon:eu:ai-act:template:article-9-risk-management-legal-text
The full legal text in the public AI Act Explorer.
Editorially reviewed | high-risk-requirements, template
- Templatev1.0.02 relations
Full text of Article 43
praxikon:eu:ai-act:template:conformity-ce-registration-legal-text
The full legal text in the public AI Act Explorer.
Editorially reviewed | conformity, template
Public generator for structuring a fundamental rights impact assessment.
Editorially reviewed | fundamental-rights, template
Public guide to GPAI model obligations and exceptions.
Hangs off: Article 53: GPAI model providers
Editorially reviewed | gpai, template
- Templatev1.0.02 relations
Full text of Article 25
praxikon:eu:ai-act:template:value-chain-representative-legal-text
The full legal text in the public AI Act Explorer.
Editorially reviewed | template, value-chain
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.