Skip to main content
Praxikon

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.

Eleven types, including evidence, control and standard.

Is about this role. Walks the role hierarchy upward.

The duty rests on this role, not merely: it is about it.

The article route this object hangs off.

Free slugs, not a taxonomy with objects of its own.

The phase of the object, not its quality.

Whether this object carries a source line of its own.

Searches label, summary, topics, conditions and statement texts. The ordering is the same heuristic as the search API; build on the identifiers, not on the ranking.

Time

Two axes. Legal time is what applied; knowledge time is what we had published by then. Leaving them empty means the default of this release.

Clear all

Objects

66 objects in this selection.

  1. 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

  2. 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

  3. 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

  4. 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

  5. Actionv1.0.04 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

  6. ActionApplicablev1.0.02 relations

    Assemble the downstream information package under Annex XII

    praxikon:eu:ai-act:action:gpai-downstream-information-package

    Build one package for providers integrating your model, covering the intended tasks and integration options, acceptable use policies, release date and distribution methods, interaction with external hardware or software, software versions, architecture and parameter count, modality and format of inputs and outputs including maximum size, licence, required technical means, and information on the training, testing and validation data used.

    Hangs off: Article 53: GPAI model providers

    Editorially reviewed | gpai

  7. ActionApplicablev1.0.02 relations

    Implement rights-reservation detection inside your copyright policy

    praxikon:eu:ai-act:action:gpai-rights-reservation-detection

    Record which techniques you use to identify a reservation of rights within the meaning of Article 4(3) of Directive (EU) 2019/790 when collecting training data, how often you recheck, and how you then comply with that reservation.

    Hangs off: Article 53: GPAI model providers

    Editorially reviewed | gpai

  8. ActionEditorialv1.0.04 relations

    Record per requirement which standard or specification you rely on, and justify every departure

    praxikon:eu:ai-act:action:justify-standards-and-specification-choices

    Keep a coverage matrix of the requirements of Section 2 against the harmonised standards, common specifications and own documents applied, noting per row the publication status in the Official Journal, and write out the Article 41(5) justification for every common specification you do not apply.

    Hangs off: Articles 40 to 42: standards, common specifications and presumption of conformity

    Editorially reviewed | conformity, standards

  9. 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

  10. 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

  11. ActionApplicablev1.0.06 relations

    Justify and record your reliance on Article 4a

    praxikon:eu:ai-act:action:record-bias-testing-legal-basis

    Only for those who themselves decide to process special categories of personal data for bias testing. In that case record which paragraph of Article 4a you rely on and whether that paragraph is open to your role, why other data do not suffice, which safeguards apply, who has access and when the data are deleted. Replace old references to Article 10(5) while you are there.

    Hangs off: Article 4a: legal basis for bias testing with special categories of personal data

    Editorially reviewed | fundamental-rights, high-risk-requirements

  12. 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

  13. Actorv1.0.071 relations

    Provider of a GPAI model

    praxikon:eu:ai-act:actor:gpai-model-provider

    A party that places a general-purpose AI model on the Union market.

    Editorially reviewed | gpai

  14. 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

  15. ChangeGuidancev1.0.13 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

  16. 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

  17. ChangeIn forcev1.0.07 relations

    Article 4a inserted, Article 10(5) deleted

    praxikon:eu:ai-act:change:2026-07-27-article-4a-inserted

    Since 27 July 2026 the legal basis for bias detection using special categories of personal data sits as Article 4a in Chapter I and no longer as Article 10(5) in Chapter III. The circle has widened from providers of high-risk systems alone to providers and deployers of other AI systems and models and deployers of high-risk systems, on the same conditions.

    Hangs off: Article 4a: legal basis for bias testing with special categories of personal data

    Placed against the official source | fundamental-rights, high-risk-requirements

  18. ChangeApplicablev1.0.05 relations

    GPAI enforcement powers active

    praxikon:eu:ai-act:change:2026-08-02-gpai-enforcement

    Since 2 August 2026 the Commission can request GPAI information, conduct evaluations and require measures.

    Hangs off: Article 53: GPAI model providers

    Placed against the official source | enforcement, gpai

  19. ChangeIn forcev1.0.03 relations

    Procedural rules for GPAI evaluations and fines in force

    praxikon:eu:ai-act:change:2026-08-10-gpai-proceedings-implementing-regulation

    Since 10 August 2026 Implementing Regulation (EU) 2026/1755 governs how the Commission evaluates general-purpose AI models and how it conducts fining proceedings.

    Hangs off: Article 53: GPAI model providers, Article 99, 100 and 101: the penalty structure per obligation

    Placed against the official source | enforcement, gpai

  20. 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

  21. 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

  22. 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

  23. 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

  24. 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

  25. ControlApplicablev1.0.05 relations

    Access and deletion control for bias testing

    praxikon:eu:ai-act:control:bias-testing-data-deletion

    The control that ensures the special categories stay with authorised people, are not transmitted, transferred or otherwise accessed by other parties, and are actually deleted once the bias has been corrected or the retention period ends, instead of lingering because nobody watches the deadline.

    Hangs off: Article 4a: legal basis for bias testing with special categories of personal data

    Editorially reviewed | fundamental-rights, high-risk-requirements

  26. ControlApplicablev1.0.02 relations

    Half-yearly review of whether your chosen compliance route still covers you

    praxikon:eu:ai-act:control:gpai-compliance-route-review

    Establish every six months whether you demonstrate compliance through a code of practice, through a published harmonised standard, or through alternative adequate means, and whether the underlying file matches that choice.

    Hangs off: Article 53: GPAI model providers

    Editorially reviewed | gpai

  27. 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

  28. 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

  29. ControlEditorialv1.0.04 relations

    Watch on publications in the Official Journal

    praxikon:eu:ai-act:control:official-journal-citation-watch

    The control that keeps the coverage matrix current: a fixed check on new references of harmonised standards, on new or amended common specifications, and on the repeal that Article 41(4) prescribes once a standard is published, with a named owner who then updates the matrix.

    Hangs off: Articles 40 to 42: standards, common specifications and presumption of conformity

    Editorially reviewed | conformity, control, standards

  30. 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

  31. DefinitionIn forcev1.0.02 relations

    Provider

    praxikon:eu:ai-act:definition:definitie-aanbieder

    The role carrying the heaviest obligations, and the role organisations most often end up in by accident.

    Placed against the official source | definitions

  32. DefinitionIn forcev1.0.03 relations

    General-purpose AI model (GPAI model)

    praxikon:eu:ai-act:definition:definitie-ai-model-voor-algemene-doeleinden

    The model is not the system, and that distinction determines which chapter of obligations applies to you.

    Placed against the official source | definitions

  33. 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

  34. 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

  35. DefinitionIn forcev1.0.03 relations

    Systemic risk

    praxikon:eu:ai-act:definition:definitie-systeemrisico

    A concept that applies exclusively to GPAI models, and that is unrelated to the high-risk classification of AI systems.

    Placed against the official source | definitions

  36. 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

  37. 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

  38. 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

  39. 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

  40. EvidenceApplicablev1.0.06 relations

    Necessity file for bias testing

    praxikon:eu:ai-act:evidence:bias-testing-necessity-record

    Per processing operation: the system or model, the paragraph of Article 4a relied on, the justification why synthetic or anonymised data do not suffice, the technical and organisational safeguards applied, the access list, the confirmation that no other party can reach the data, and the deletion date. This is also the text that paragraph 1, point (f), requires in the record of processing activities.

    Hangs off: Article 4a: legal basis for bias testing with special categories of personal data

    Editorially reviewed | fundamental-rights, high-risk-requirements

  41. Evidencev1.0.04 relations

    GPAI compliance file

    praxikon:eu:ai-act:evidence:gpai-compliance-file

    Current technical documentation, downstream information, copyright policy and public training summary.

    Hangs off: Article 53: GPAI model providers

    Editorially reviewed | evidence, gpai

  42. EvidenceApplicablev1.0.02 relations

    Model version register listing the changed Annex XI and XII elements per version

    praxikon:eu:ai-act:evidence:gpai-model-version-register

    A register with one row per model version: release date, distribution method, architecture and parameter count, compute used, and a note of which Annex XI and Annex XII elements changed relative to the previous version.

    Hangs off: Article 53: GPAI model providers

    Editorially reviewed | gpai

  43. EvidenceApplicablev1.0.02 relations

    Public summary of training content following the AI Office template

    praxikon:eu:ai-act:evidence:gpai-public-training-summary

    The published, sufficiently detailed summary of the content used to train the model, drawn up according to the template provided by the AI Office, with publication date and the corresponding model version.

    Hangs off: Article 53: GPAI model providers

    Editorially reviewed | gpai

  44. 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

  45. EvidenceEditorialv1.0.04 relations

    Coverage matrix and justification for standards and specifications

    praxikon:eu:ai-act:evidence:standards-conformity-justification-file

    Per requirement of Section 2: the harmonised standard or common specification applied with its version, the publication status of the reference in the Official Journal, what the standard or specification does and does not cover, and on departure the Article 41(5) justification with the technical solution chosen and the test showing equivalence.

    Hangs off: Articles 40 to 42: standards, common specifications and presumption of conformity

    Editorially reviewed | conformity, evidence, standards

  46. 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

  47. 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

  48. GuidanceGuidancev1.0.13 relations

    When a downstream party that fine-tunes becomes a GPAI provider itself

    praxikon:eu:ai-act:guidance:guidance-gpai-downstream-modifier-becomes-provider

    Not every modification makes you a provider. The indicative threshold is a modification using more than a third of the original model's training compute, and your obligations are then limited to the modification.

    Hangs off: Article 53: GPAI model providers

    Placed against the official source | guidance

  49. ObligationApplicablev1.0.413 relations

    Articles 40 to 42: standards, common specifications and presumption of conformity

    praxikon:eu:ai-act:obligation:article-40-42-standards-and-specifications

    A party applying a harmonised standard whose reference has been published in the Official Journal of the European Union is presumed to be in conformity with the requirements of Section 2 or with the obligations of Chapter V, Sections 2 and 3, to the extent that the standard covers them. Where no such standard exists and the conditions of Article 41(1) are fulfilled, the Commission may adopt common specifications by implementing act, and those carry the same presumption. If you do not apply such a common specification, you must duly justify that you have adopted technical solutions that are at least equivalent. Article 42 adds three narrow presumptions, and they do not all arise in the same way. Paragraph 1 gives the presumption of conformity with Article 10(4) to systems trained and tested on data reflecting the specific geographical, behavioural, contextual or functional setting within which they are intended to be used; no publication in the Official Journal is attached to it. Paragraph 2 does carry that condition: the presumption of conformity with the cybersecurity requirements of Article 15 applies to systems certified under a scheme pursuant to Regulation (EU) 2019/881 the references of which have been published in the Official Journal. The paragraph 3 added by Article 1, point (18), of Regulation (EU) 2026/1744 gives that same presumption to systems falling within the scope of Regulation (EU) 2024/2847 that meet the conditions in Article 12(1) thereof. Each of these presumptions is rebuttable and reaches no further than what the standard, the specification or the certification covers.

    Placed against the official source | conformity, standards

  50. ObligationApplicablev1.0.116 relations

    Article 4a: legal basis for bias testing with special categories of personal data

    praxikon:eu:ai-act:obligation:article-4a-bias-testing-legal-basis

    Article 4a grants permission rather than instruction, and to two different sets of parties. Paragraph 1 allows only the provider of a high-risk AI system to process special categories of personal data by way of exception, to the extent strictly necessary for bias detection and correction within the meaning of Article 10(2), points (f) and (g), and only where all six conditions (a) to (f) are met. Paragraph 2 opens the same room to providers and deployers of other AI systems and models and to deployers of high-risk systems, but only for bias likely to affect the health and safety of persons, to have a negative impact on fundamental rights or to lead to discrimination prohibited under Union law, and subject to the same six conditions. Until 27 July 2026 this basis sat in Article 10(5).

    Placed against the official source | fundamental-rights, high-risk-requirements

  51. ObligationApplicablev1.0.215 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

  52. ObligationApplicablev1.0.029 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

  53. 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

  54. 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

  55. 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

  56. 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

  57. ObligationApplicablev1.1.017 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

  58. TemplateApplicablev1.0.04 relations

    Full text of Articles 40, 41 and 42

    praxikon:eu:ai-act:template:article-40-42-legal-text

    The full legal text of the standards and specifications provisions in the public AI Act Explorer.

    Hangs off: Articles 40 to 42: standards, common specifications and presumption of conformity

    Editorially reviewed | conformity, standards, template

  59. TemplateApplicablev1.0.05 relations

    Full text of Article 4a

    praxikon:eu:ai-act:template:article-4a-legal-text

    The full text of Article 4a as inserted and published in the Official Journal of 24 July 2026.

    Hangs off: Article 4a: legal basis for bias testing with special categories of personal data

    Editorially reviewed | fundamental-rights, high-risk-requirements

  60. 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

  61. 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

  62. 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

  63. 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

  64. 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

  65. 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

  66. Templatev1.0.03 relations

    GPAI obligations route

    praxikon:eu:ai-act:template:gpai-guide

    Public guide to GPAI model obligations and exceptions.

    Hangs off: Article 53: GPAI model providers

    Editorially reviewed | gpai, 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.