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

31 objects in this selection.

  1. ObligationUpcomingv1.0.019 relations

    Annex III: the eight areas separately

    praxikon:eu:ai-act:obligation:annex-iii-eight-areas

    Annex III names eight areas in which an AI system can be high-risk under Article 6(2). This object publishes those eight areas as separate objects, so that a question about recruitment, assessment, creditworthiness or border control lands on the point that names it rather than on the list as a whole.

    Placed against the official source | high-risk

  2. ObligationUpcomingv1.0.018 relations

    Annex III: high-risk AI

    praxikon:eu:ai-act:obligation:annex-iii-high-risk

    Classification route for standalone high-risk AI systems under Article 6(2) and Annex III.

    Placed against the official source | high-risk

  3. ObligationUpcomingv1.0.011 relations

    Article 10: data and data governance

    praxikon:eu:ai-act:obligation:article-10-data-governance

    Quality and governance requirements for training, validation and test data of high-risk AI.

    Placed against the official source | high-risk-requirements

  4. ObligationUpcomingv1.0.011 relations

    Article 11: technical documentation

    praxikon:eu:ai-act:obligation:article-11-technical-documentation

    The technical file demonstrating before market placement that a high-risk system meets the requirements.

    Placed against the official source | high-risk-requirements

  5. ObligationApplicablev1.0.016 relations

    Article 111(2): legacy high-risk systems and the 2 August 2030 date

    praxikon:eu:ai-act:obligation:article-111-legacy-public-systems

    High-risk AI systems placed on the market or put into service before the date of application of Chapter III, since the Digital Omnibus 2 December 2027 for Annex III systems and 2 August 2028 for Annex I systems, come under the high-risk requirements of that Chapter only once their design is significantly changed as from that date. This is not an exemption from the whole Regulation: Article 4 and Article 50 keep running. For systems intended to be used by public authorities the carve out falls away entirely: their providers and deployers must in any case comply with the requirements and obligations by 2 August 2030.

    Placed against the official source | high-risk, timeline

  6. ObligationUpcomingv1.0.014 relations

    Article 12: logging and traceability

    praxikon:eu:ai-act:obligation:article-12-logging

    Automatic recording of events over the lifetime of a high-risk AI system.

    Placed against the official source | high-risk-requirements

  7. ObligationUpcomingv1.0.010 relations

    Article 13: transparency towards deployers

    praxikon:eu:ai-act:obligation:article-13-instructions

    Comprehensible instructions for use and system information so deployers can operate the system correctly.

    Placed against the official source | high-risk-requirements

  8. ObligationUpcomingv1.0.011 relations

    Article 14: human oversight

    praxikon:eu:ai-act:obligation:article-14-human-oversight

    High-risk AI must be designed so that humans can effectively oversee it and intervene.

    Placed against the official source | high-risk-requirements

  9. ObligationUpcomingv1.0.010 relations

    Article 15: accuracy, robustness and cybersecurity

    praxikon:eu:ai-act:obligation:article-15-accuracy-robustness

    Appropriate levels of performance, robustness and security across the lifecycle of high-risk AI.

    Placed against the official source | high-risk-requirements

  10. ObligationUpcomingv1.0.011 relations

    Article 17: quality management system

    praxikon:eu:ai-act:obligation:article-17-quality-management

    The documented quality system through which a high-risk AI provider structurally assures compliance.

    Placed against the official source | high-risk-requirements

  11. ObligationUpcomingv1.0.011 relations

    Article 18: documentation keeping

    praxikon:eu:ai-act:obligation:article-18-document-retention

    The provider of a high-risk AI system keeps the technical documentation, the quality management system documentation, the changes approved by notified bodies and the decisions they issued, and the EU declaration of conformity at the disposal of the national competent authorities for a period ending ten years after the system has been placed on the market or put into service.

    Placed against the official source | high-risk-requirements

  12. ObligationUpcomingv1.0.019 relations

    Article 27: FRIA

    praxikon:eu:ai-act:obligation:article-27-fria

    Fundamental rights impact assessment before deploying certain high-risk AI systems.

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

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

  14. ObligationApplicablev2.0.019 relations

    Article 4: AI literacy

    praxikon:eu:ai-act:obligation:article-4-ai-literacy

    Providers and deployers take measures that support the development of AI literacy.

    Placed against the official source | ai-literacy

  15. ObligationApplicablev1.0.016 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

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

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

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

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

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

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

  22. ObligationUpcomingv1.0.011 relations

    Article 6(1): the product route to high risk

    praxikon:eu:ai-act:obligation:article-6-1-annex-i-product-route

    An AI system counts as high risk where it is intended to be used as a safety component of a product covered by the Union harmonisation legislation listed in Annex I, or is itself such a product, and that product is required to undergo a third-party conformity assessment. This route does not run through Annex III but through the product legislation that already applies to the product. For Section A products the requirements of Chapter III, Section 2, form part of the sectoral assessment under Article 43(3); for Section B products Article 2(2) limits the operation of this Regulation to a short list of provisions.

    Placed against the official source | conformity, high-risk

  23. ObligationIn forcev1.0.010 relations

    Article 6(1a) to (1c): the tightened classification route

    praxikon:eu:ai-act:obligation:article-6-1bis-1quater-route

    The Digital Omnibus inserts three paragraphs into Article 6 that draw the notion of safety component more tightly: which AI systems do not qualify as safety components, which still do despite that exclusion because failure would endanger health and safety, and which mandatory third-party conformity assessment does not count. Paragraph 1a is written for the purposes of the Regulation as a whole and therefore bears on both the Annex I route and Annex III, point 2.

    Placed against the official source | conformity, high-risk

  24. ObligationUpcomingv1.0.013 relations

    Article 71: EU database for high-risk AI systems listed in Annex III

    praxikon:eu:ai-act:obligation:article-71-eu-database

    The provider or, where applicable, the authorised representative enters the data listed in Sections A and B of Annex VIII into the EU database; the deployer who is, or who acts on behalf of, a public authority, agency or body enters the data listed in Section C. Information registered in accordance with Article 49 is publicly available in a user-friendly manner and machine-readable, except for the secure section covering law enforcement, migration, asylum and border control management and the registration of testing in real world conditions. Setting up and maintaining the database itself is a task of the Commission and not a duty of yours.

    Placed against the official source | conformity, high-risk

  25. ObligationApplicablev2.0.015 relations

    Article 72: post-market monitoring

    praxikon:eu:ai-act:obligation:article-72-post-market-monitoring

    Systematic monitoring of high-risk AI in real use, after market placement.

    Placed against the official source | post-market

  26. ObligationApplicablev2.0.015 relations

    Article 73: serious incident reporting

    praxikon:eu:ai-act:obligation:article-73-incident-reporting

    The duty to report serious incidents with high-risk AI, under strict deadlines.

    Placed against the official source | post-market

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

  28. ObligationUpcomingv1.0.010 relations

    Article 8: compliance with the requirements for high-risk AI systems

    praxikon:eu:ai-act:obligation:article-8-compliance-with-requirements

    High-risk AI systems comply with the requirements of Chapter III, Section 2, and that is assessed taking into account the intended purpose and the generally acknowledged state of the art on AI and AI-related technologies, with the risk management system of Article 9 as the instrument. Where the system sits in a product also covered by the Union harmonisation legislation of Section A of Annex I, the provider is responsible for full compliance with all applicable requirements of that legislation, and may integrate the testing and reporting processes and the information and documentation on the product into the documentation and procedures that already exist there.

    Placed against the official source | conformity, high-risk-requirements

  29. ObligationUpcomingv1.0.010 relations

    Article 9: risk management system

    praxikon:eu:ai-act:obligation:article-9-risk-management

    A continuous, documented risk management system across the entire lifecycle of a high-risk AI system.

    Placed against the official source | high-risk-requirements

  30. ObligationApplicablev2.0.018 relations

    Articles 43-49: conformity assessment, CE and registration

    praxikon:eu:ai-act:obligation:conformity-ce-registration

    The route from assessment to CE marking and EU database registration before market placement of high-risk AI.

    Placed against the official source | conformity

  31. ObligationUpcomingv1.0.011 relations

    Articles 22-25: value chain and authorised representative

    praxikon:eu:ai-act:obligation:value-chain-representative

    Role shifts in the AI value chain and the mandatory representative for non-EU providers.

    Placed against the official source | 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.