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.
Objects
18 objects in this selection.
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- 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
Fundamental rights impact assessment before deploying certain high-risk AI systems.
Placed against the official source | fundamental-rights, high-risk
- 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
- 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
- ObligationApplicablev1.0.015 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.014 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
- ObligationUpcomingv1.0.014 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
- ObligationUpcomingv1.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
- 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
- ObligationUpcomingv1.0.015 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
- 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.