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

18 objects in this selection.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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