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

33 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.066 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.013 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.020 relations

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

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

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

    Placed against the official source | high-risk, timeline

  6. ObligationUpcomingv1.0.015 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.011 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.012 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.012 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.010 relations

    Article 16: the twelve duties of a provider of a high-risk AI system

    praxikon:eu:ai-act:obligation:article-16-provider-obligations

    Article 16 is the summary list of duties for providers: twelve points that route onward to the quality management system, the documentation, the logs, the conformity assessment, the EU declaration of conformity, the CE marking, the registration, corrective actions and accessibility requirements.

    Placed against the official source | high-risk-requirements

  11. ObligationUpcomingv1.0.014 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

  12. ObligationUpcomingv1.0.012 relations

    Article 18: documentation keeping

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

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

    Placed against the official source | high-risk-requirements

  13. ObligationUpcomingv1.0.015 relations

    Article 20: corrective actions and duty of information

    praxikon:eu:ai-act:obligation:article-20-corrective-actions

    A provider that considers, or has reason to consider, that a high-risk AI system it has placed on the market or put into service is not in conformity with the Regulation must immediately take the necessary corrective actions and inform the distributors accordingly, and, where applicable, also the deployers, the authorised representative and the importers. Where that system also presents a risk within the meaning of Article 79(1), the provider must immediately investigate the causes and inform the competent market surveillance authorities and, where applicable, the notified body that issued a certificate under Article 44.

    Placed against the official source | high-risk-requirements, post-market

  14. ObligationUpcomingv1.0.012 relations

    Article 21: cooperation with competent authorities

    praxikon:eu:ai-act:obligation:article-21-cooperation-with-authorities

    Upon a reasoned request by a competent authority, the provider of a high-risk AI system provides all the information and documentation necessary to demonstrate conformity with the requirements of Chapter III, Section 2, in a language which can be easily understood by the authority in one of the official languages of the institutions of the Union as indicated by the Member State concerned. Upon the same request the provider also gives, as applicable, access to the automatically generated logs, to the extent those logs are under its control.

    Placed against the official source | high-risk-requirements

  15. ObligationApplicablev2.0.046 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

  16. ObligationApplicablev1.0.213 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. As long as no such standard exists, 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

  17. ObligationApplicablev1.0.017 relations

    Article 49: registration in the EU database before the system reaches the market

    praxikon:eu:ai-act:obligation:article-49-registration

    The provider of a high-risk AI system listed in Annex III, or where applicable its authorised representative, registers itself and that system in the EU database before it is placed on the market or put into service. The same duty applies to the provider that concludes under Article 6(3) that its Annex III system is precisely not high-risk: that provider too registers itself and that system. The deployer that is a public authority or a Union body, or that acts on behalf of such an authority, registers itself, selects the system and registers its use. For the areas of law enforcement, migration, asylum and border control management the registration goes into a secure non-public section with fewer fields, to which only the Commission and the national authorities referred to in Article 74(8) have access. For the systems in point 2 of Annex III registration does not run through the EU database but at national level.

    Placed against the official source | conformity, high-risk

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

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

  20. ObligationApplicablev1.0.049 relations

    Article 50: transparency

    praxikon:eu:ai-act:obligation:article-50-transparency

    Specific disclosure, marking and labelling duties for certain AI systems and synthetic content.

    Placed against the official source | transparency

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

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

  23. ObligationApplicablev1.0.012 relations

    Article 60: testing in real world conditions outside a sandbox

    praxikon:eu:ai-act:obligation:article-60-real-world-testing

    If you want to test an Annex III high-risk AI system with real people and real outcomes before placing it on the market, a full regime applies: a plan, prior approval by the market surveillance authority, registration, informed consent and a maximum duration.

    Placed against the official source | innovation

  24. ObligationApplicablev1.0.012 relations

    Article 61: informed consent of test subjects for testing in real world conditions

    praxikon:eu:ai-act:obligation:article-61-informed-consent

    If you test a high-risk AI system in real world conditions outside an AI regulatory sandbox, freely-given informed consent must be obtained from every test subject before they participate. Beforehand the subject receives concise, clear, relevant and understandable information on five prescribed topics: the nature and objectives of the testing and the possible inconvenience, the conditions under which the testing is to be conducted including the expected duration of participation, their rights and guarantees including the right to refuse and the right to withdraw at any time without detriment and without justification, the arrangements for requesting the reversal or the disregarding of the outputs of the system, and the Union-wide unique single identification number with the contact details from whom further information can be obtained. The consent is dated and documented and the subject is given a copy.

    Placed against the official source | fundamental-rights, innovation

  25. ObligationUpcomingv1.0.015 relations

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

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

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

    Placed against the official source | conformity, high-risk

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

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

  28. ObligationUpcomingv1.0.012 relations

    Article 75(1a) and (1e): reporting to and assessment by the AI Office

    praxikon:eu:ai-act:obligation:article-75-ai-office-high-risk-duties

    If you are the provider of a high-risk AI system subject to the competence of the AI Office, you report serious incidents to the Office rather than to your national authority, with the machinery and the deadlines of Article 73(2) to (9) applying in full, and the Office still transmits the information to your national market surveillance authority. Where that system is subject to a third-party conformity assessment under Article 43, the Office is responsible for it, the notified body acts on behalf of the Commission, and you pay the costs directly to that body.

    Placed against the official source | enforcement, governance, high-risk-requirements

  29. ObligationApplicablev1.0.113 relations

    Article 75: market surveillance, mutual assistance and the powers of the AI Office

    praxikon:eu:ai-act:obligation:article-75-market-surveillance-assistance

    For a defined group of AI systems the AI Office is exclusively competent for supervision and enforcement instead of the national market surveillance authority. The Office can request information by simple request or by decision, open investigations, carry out remote and on-site inspections, make commitments binding, and impose both fines through Article 99 and periodic penalty payments. Four groups are carved out; there a national authority remains competent.

    Placed against the official source | enforcement, governance, gpai

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

  31. ObligationUpcomingv1.0.013 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

  32. ObligationApplicablev2.0.041 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

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