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

22 objects in this selection.

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

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

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

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

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

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

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

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

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

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

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

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

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

  14. ExampleGuidancev1.0.02 relations

    Heavy fine-tuning makes you the model provider

    praxikon:eu:ai-act:example:example-finetunen-boven-de-compute-drempel

    A European scale-up fine-tunes an existing general-purpose AI model for its own product, using more compute than one third of the compute used to train the original model.

    Hangs off: Article 53: GPAI model providers

    Placed against the official source | examples

  15. ExampleGuidancev1.0.03 relations

    Light fine-tuning does not make you a model provider

    praxikon:eu:ai-act:example:example-lichte-finetuning-geen-modelaanbieder

    A bank fine-tunes an existing general-purpose AI model on its own product documentation and customer questions, using a fraction of the original compute, and builds a customer chatbot around it that it offers under its own name.

    Hangs off: Article 53: GPAI model providers

    Placed against the official source | examples

  16. ExampleGuidancev1.0.02 relations

    Modifying a systemic-risk model pulls the heaviest duties to you

    praxikon:eu:ai-act:example:example-model-met-systeemrisico-aanpassen

    A downstream actor modifies an existing systemic-risk model so substantially that the change exceeds the threshold, and publishes the result as its own model.

    Hangs off: Article 53: GPAI model providers

    Placed against the official source | examples

  17. ExampleGuidancev1.0.02 relations

    Open source in name, but not within the meaning of the Regulation

    praxikon:eu:ai-act:example:example-opensource-in-naam-maar-niet-in-de-zin-van-de-verordening

    Three providers call their model open source. The first licence allows non-commercial research only. The second requires a separate commercial licence once monthly active users pass a threshold. The third gives the model away for free but hosts it exclusively on its own platform where visitors are served paid advertisements.

    Hangs off: Article 53: GPAI model providers

    Placed against the official source | examples

  18. ExampleGuidancev1.0.02 relations

    What the open-source exemption does and does not cover

    praxikon:eu:ai-act:example:example-opensource-uitzondering-reikwijdte

    A research group publishes a general-purpose AI model under a free and open-source licence and makes the weights, architecture and usage information publicly available. The model carries no systemic risk.

    Hangs off: Article 53: GPAI model providers

    Placed against the official source | examples

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

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

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

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