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
2 objects in this selection.
- ChangeApplicablev1.0.04 relations
The AI Act enters into force
praxikon:eu:ai-act:change:2024-08-01-entry-into-force
The regulation entered into force on 1 August 2024, after which the obligations followed in phases.
Hangs off: Article 4: AI literacy, Article 5: prohibited practices
Placed against the official source | timeline
- ChangeApplicablev1.0.04 relations
Prohibited practices and AI literacy apply
praxikon:eu:ai-act:change:2025-02-02-prohibitions-and-literacy-applicable
Since 2 February 2025 the Article 5 prohibition and the Article 4 AI literacy duty apply.
Hangs off: Article 4: AI literacy, Article 5: prohibited practices
Placed against the official source | ai-literacy, timeline
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.