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

150 of 285 shown. Pick a type below or narrow with a filter to see the rest.

  1. Actionv1.0.05 relations

    Classify the use case and document the outcome

    praxikon:eu:ai-act:action:annex-iii-classify

    Assess Article 5, Article 6 and Annex III in that order and document purpose, context and any Article 6(3) exception.

    Hangs off: Annex III: high-risk AI

    Editorially reviewed | high-risk

  2. ActionUpcomingv1.0.03 relations

    Assign human oversight and give those people a mandate

    praxikon:eu:ai-act:action:appoint-and-empower-human-oversight

    Name, per high-risk system, who exercises oversight, and ensure that person has the competence, training, authority and support to actually set the output aside.

    Hangs off: Article 26: obligations of deployers of high-risk AI systems

    Editorially reviewed | high-risk-requirements

  3. Actionv1.0.04 relations

    Set up data governance per dataset

    praxikon:eu:ai-act:action:article-10-data-governance-act

    Assess origin, representativeness, errors and completeness and examine possible bias with appropriate mitigation.

    Hangs off: Article 10: data and data governance

    Editorially reviewed | high-risk-requirements

  4. Actionv1.0.04 relations

    Design logging into the system

    praxikon:eu:ai-act:action:article-12-logging-act

    Ensure the system automatically records events relevant to risk identification and post-market monitoring.

    Hangs off: Article 12: logging and traceability

    Editorially reviewed | high-risk-requirements

  5. Actionv1.0.04 relations

    Provide complete instructions for use

    praxikon:eu:ai-act:action:article-13-instructions-act

    Describe capabilities, limitations, accuracy, oversight measures and expected lifetime in comprehensible form.

    Hangs off: Article 13: transparency towards deployers

    Editorially reviewed | high-risk-requirements

  6. Actionv1.0.04 relations

    Design and assign effective human oversight

    praxikon:eu:ai-act:action:article-14-human-oversight-act

    Determine oversight measures per system, appoint competent persons and give them the mandate to intervene or stop.

    Hangs off: Article 14: human oversight

    Editorially reviewed | high-risk-requirements

  7. Actionv1.0.05 relations

    Take role- and context-specific AI literacy measures

    praxikon:eu:ai-act:action:article-4-measures

    Determine for each role, system and context which combination of instruction, guidance, practice or training is appropriate.

    Hangs off: Article 4: AI literacy

    Editorially reviewed | ai-literacy

  8. ActionApplicablev1.0.03 relations

    Determine per role which knowledge is needed to use the specific system responsibly

    praxikon:eu:ai-act:action:article-4-role-needs-matrix

    Map roles against the AI systems they use and record per combination what a person must be able to judge: what the system does, where it fails, who it is applied to, and when to intervene or escalate.

    Hangs off: Article 4: AI literacy

    Editorially reviewed | ai-literacy

  9. ActionApplicablev1.0.03 relations

    Deliver instruction at the moment a new tool or a new employee arrives

    praxikon:eu:ai-act:action:article-4-tool-and-onboarding-instruction

    Attach the literacy measure to two fixed moments in existing processes: the rollout of a new AI tool and the onboarding of anyone gaining access to an existing tool.

    Hangs off: Article 4: AI literacy

    Editorially reviewed | ai-literacy

  10. Actionv1.0.04 relations

    Screen every use case against Article 5 first

    praxikon:eu:ai-act:action:article-5-screen

    Before procurement, build or deployment, check whether the use case falls under a prohibited practice and stop or redesign early rather than after the fact.

    Hangs off: Article 5: prohibited practices

    Editorially reviewed | prohibited-practices

  11. Actionv1.0.05 relations

    Implement the applicable disclosure, marking or label

    praxikon:eu:ai-act:action:article-50-disclosure

    First determine which paragraph of Article 50 applies, then implement the specific transparency measure.

    Hangs off: Article 50: transparency

    Editorially reviewed | transparency

  12. ActionApplicablev1.0.02 relations

    Record per publication channel when AI text carries a disclosure and who holds editorial responsibility

    praxikon:eu:ai-act:action:article-50-editorial-labelling-policy

    Determine per channel whether the text is published to inform the public on matters of public interest, who performs the human review, who holds editorial responsibility, and which standard wording you use when the disclosure is required.

    Hangs off: Article 50: transparency

    Editorially reviewed | transparency

  13. ActionApplicablev1.0.03 relations

    Test every system in your AI register against the five Article 50 scenarios

    praxikon:eu:ai-act:action:article-50-scenario-triage

    For each AI system, walk through the distinct Article 50 scenarios (direct interaction, synthetic output, emotion recognition or biometric categorisation, deep fake, published text on matters of public interest) and record per paragraph whether it applies, does not apply or falls under an exception, with the reason.

    Hangs off: Article 50: transparency

    Editorially reviewed | transparency

  14. ActionApplicablev1.0.04 relations

    Apply to a sandbox and agree the sandbox plan

    praxikon:eu:ai-act:action:article-57-sandbox-application-and-plan

    Apply to the competent authority, agree a specific sandbox plan, and record which uncertainty about the Regulation you want resolved inside the sandbox.

    Hangs off: Article 57: AI regulatory sandboxes

    Editorially reviewed | innovation

  15. ActionApplicablev1.0.05 relations

    Submit the testing plan, obtain approval and register the test

    praxikon:eu:ai-act:action:article-60-testing-plan-and-authorisation

    Draw up a real-world testing plan, submit it to the market surveillance authority, obtain approval, register the test with a Union-wide unique single identification number, and record the division of roles with your deployer.

    Hangs off: Article 60: testing in real world conditions outside a sandbox

    Editorially reviewed | innovation

  16. Actionv1.0.04 relations

    Draw up a post-market monitoring plan

    praxikon:eu:ai-act:action:article-72-post-market-monitoring-act

    Systematically collect and analyse real-world data on the system’s performance and compliance throughout its lifetime.

    Hangs off: Article 72: post-market monitoring

    Editorially reviewed | post-market

  17. Actionv1.0.04 relations

    Set up an incident process with reporting routes

    praxikon:eu:ai-act:action:article-73-incident-reporting-act

    Define what a serious incident is, assign the reporting route to the supervisor and rehearse the process.

    Hangs off: Article 73: serious incident reporting

    Editorially reviewed | post-market

  18. Actionv1.0.04 relations

    Complete the conformity route before market placement

    praxikon:eu:ai-act:action:conformity-ce-registration-act

    Select the correct assessment procedure, draw up the EU declaration of conformity, affix the CE marking and register in the EU database.

    Hangs off: Articles 43-49: conformity assessment, CE and registration

    Editorially reviewed | conformity

  19. ActionUpcomingv1.0.04 relations

    Map the affected groups and their specific risks of harm

    praxikon:eu:ai-act:action:fria-affected-groups-analysis

    Name the categories of natural persons and groups likely to be affected by the use in this specific context, and work out the specific risks of harm per category, using the information the provider supplied under Article 13.

    Hangs off: Article 27: FRIA

    Editorially reviewed | fundamental-rights

  20. Actionv1.0.06 relations

    Perform a FRIA before deployment

    praxikon:eu:ai-act:action:fria-assess

    Assess process, duration, affected persons, risks, oversight, mitigation and complaint mechanisms and notify results where required.

    Hangs off: Article 27: FRIA

    Editorially reviewed | fundamental-rights, high-risk

  21. ActionUpcomingv1.0.04 relations

    Set up the complaint mechanism and internal governance before the system runs

    praxikon:eu:ai-act:action:fria-complaint-mechanism-setup

    Describe the measures taken if a risk materialises, who decides internally, through which route an affected person can complain, within which deadline you respond, and who is authorised to stop the use.

    Hangs off: Article 27: FRIA

    Editorially reviewed | fundamental-rights

  22. ActionApplicablev1.0.03 relations

    Set up how you handle a request for an explanation

    praxikon:eu:ai-act:action:handle-explanation-requests

    Ensure your complaints or objections desk recognises a request for an explanation of an AI-supported decision, that it can be traced per decision which system in which version contributed to it, and that someone is designated to give the explanation.

    Hangs off: Article 86: right to an explanation of a decision

    Editorially reviewed | fundamental-rights

  23. ActionApplicablev1.0.03 relations

    Make sure you can answer a complaint with documents

    praxikon:eu:ai-act:action:prepare-for-a-complaint

    Record per AI system which assessment was carried out, by whom, on what date and against which system version, and agree who receives a question from the authority and within what period.

    Hangs off: Article 85: right to lodge a complaint with the market surveillance authority

    Editorially reviewed | fundamental-rights

  24. Actionv1.0.04 relations

    Assess the value-chain role per system and change

    praxikon:eu:ai-act:action:value-chain-representative-act

    On white-labelling, substantial modification or purpose change, assess whether your organisation becomes the provider, and arrange the representative for non-EU supply.

    Hangs off: Articles 22-25: value chain and authorised representative

    Editorially reviewed | value-chain

  25. Actorv1.0.014 relations

    Credit or insurance deployer

    praxikon:eu:ai-act:actor:credit-or-insurance-deployer

    A deployer of the relevant creditworthiness or life and health insurance systems in Annex III point 5(b) or 5(c).

    Editorially reviewed | fundamental-rights, high-risk

  26. Actorv1.0.0273 relations

    Deployer

    praxikon:eu:ai-act:actor:deployer

    An organisation using an AI system under its authority, excluding personal non-professional use.

    Editorially reviewed | governance

  27. Actorv1.0.033 relations

    Body governed by public law

    praxikon:eu:ai-act:actor:public-law-body

    A deployer that is a body governed by public law.

    Editorially reviewed | fundamental-rights

  28. Actorv1.0.015 relations

    Private provider of public services

    praxikon:eu:ai-act:actor:public-service-provider

    A private deployer providing public services.

    Editorially reviewed | fundamental-rights

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

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

  31. ChangeGuidancev1.0.04 relations

    Guidelines on the definition of an AI system

    praxikon:eu:ai-act:change:2025-07-29-ai-system-definition-guidelines

    The Commission draws the line between software that does and does not fall under the regulation.

    Hangs off: Annex III: high-risk AI, Article 4: AI literacy

    Placed against the official source | scope

  32. ChangeGuidancev1.0.03 relations

    Guidelines on prohibited AI practices

    praxikon:eu:ai-act:change:2025-07-29-prohibited-practices-guidelines

    Worked examples for each Article 5 prohibition, with the line between permitted and prohibited.

    Hangs off: Article 5: prohibited practices

    Placed against the official source | prohibited

  33. ChangeGuidancev1.0.04 relations

    Draft guidelines on high-risk classification

    praxikon:eu:ai-act:change:2026-05-19-draft-high-risk-guidelines

    The Commission explains in consultation when a system falls under Annex I or Annex III.

    Hangs off: Annex III: high-risk AI, Articles 43-49: conformity assessment, CE and registration

    Placed against the official source | high-risk

  34. ChangeGuidancev1.0.03 relations

    Transparency Code of Practice published

    praxikon:eu:ai-act:change:2026-06-10-transparency-code-of-practice

    A voluntary route to comply with parts of Article 50, in two separately signable sections.

    Hangs off: Article 50: transparency

    Placed against the official source | transparency

  35. ChangeGuidancev1.0.03 relations

    Final guidelines on Article 50

    praxikon:eu:ai-act:change:2026-07-20-article-50-guidelines

    The Commission works out the transparency duties and confirms they apply from 2 August 2026.

    Hangs off: Article 50: transparency

    Placed against the official source | transparency

  36. ChangeIn forcev1.0.05 relations

    Annex III core rules moved to 2 December 2027

    praxikon:eu:ai-act:change:2026-07-27-annex-iii-date

    The amended application date has been binding law since 27 July 2026.

    Hangs off: Annex III: high-risk AI

    Placed against the official source | high-risk

  37. ChangeIn forcev1.0.05 relations

    Article 4 amended to a duty to take measures

    praxikon:eu:ai-act:change:2026-07-27-article-4-amended

    Since 27 July 2026 the organisational duty supports the development of AI literacy without guaranteeing an individual level.

    Hangs off: Article 4: AI literacy

    Placed against the official source | ai-literacy

  38. ChangeIn forcev1.0.06 relations

    FRIA follows new date and may cross-reference a DPIA

    praxikon:eu:ai-act:change:2026-07-27-fria-date-and-dpia-link

    The FRIA for the relevant Annex III route follows 2 December 2027 and may include or cross-reference relevant DPIA elements.

    Hangs off: Article 27: FRIA

    Placed against the official source | fundamental-rights, high-risk

  39. ChangeApplicablev1.0.05 relations

    Article 50 is applicable

    praxikon:eu:ai-act:change:2026-08-02-article-50-applicable

    The transparency duties apply since 2 August 2026.

    Hangs off: Article 50: transparency

    Placed against the official source | transparency

  40. Controlv1.0.04 relations

    Reclassification on purpose or context change

    praxikon:eu:ai-act:control:annex-iii-change-trigger

    Reopen classification when intended purpose, use context or system functionality changes materially.

    Hangs off: Annex III: high-risk AI

    Editorially reviewed | control, high-risk

  41. ControlUpcomingv1.0.03 relations

    Procurement gate: no signature without a completed classification answer

    praxikon:eu:ai-act:control:annex-iii-procurement-gate

    Block signature of an AI contract until the supplier has answered in writing which Annex III point the intended purpose falls under, whether it relies on Article 6(3), and whether the system profiles natural persons.

    Hangs off: Annex III: high-risk AI

    Editorially reviewed | high-risk

  42. Controlv1.0.04 relations

    Data check before retraining

    praxikon:eu:ai-act:control:article-10-data-governance-control

    Repeat the data quality assessment before every retraining or dataset change.

    Hangs off: Article 10: data and data governance

    Editorially reviewed | control, high-risk-requirements

  43. Controlv1.0.04 relations

    Periodic log review

    praxikon:eu:ai-act:control:article-12-logging-control

    Periodically verify that logging works, is complete and is retained according to the regime.

    Hangs off: Article 12: logging and traceability

    Editorially reviewed | control, high-risk-requirements

  44. Controlv1.0.04 relations

    Instructions check at deployment

    praxikon:eu:ai-act:control:article-13-instructions-control

    At every deployment and update, verify instructions are present, current and internally translated.

    Hangs off: Article 13: transparency towards deployers

    Editorially reviewed | control, high-risk-requirements

  45. Controlv1.0.04 relations

    Oversight test before go-live

    praxikon:eu:ai-act:control:article-14-human-oversight-control

    Before go-live, test that intervening, stopping and disregarding output actually works and is assigned.

    Hangs off: Article 14: human oversight

    Editorially reviewed | control, high-risk-requirements

  46. ControlApplicablev1.0.03 relations

    Coverage reconciliation: every person with AI access appears in the register

    praxikon:eu:ai-act:control:article-4-coverage-reconciliation

    Periodically reconcile the list of accounts and licences with access to AI systems against the participation and instruction register, and clear the gap list with an owner and a deadline.

    Hangs off: Article 4: AI literacy

    Editorially reviewed | ai-literacy

  47. Controlv1.0.04 relations

    Periodic role and context review

    praxikon:eu:ai-act:control:article-4-periodic-review

    Check when systems, roles or risks change whether the selected measures remain appropriate.

    Hangs off: Article 4: AI literacy

    Editorially reviewed | ai-literacy, control

  48. Controlv1.0.04 relations

    Article 5 gate at intake and change

    praxikon:eu:ai-act:control:article-5-intake-gate

    Repeat the screening for every new system, procurement and material change of purpose or context; an earlier clearance does not cover a new use.

    Hangs off: Article 5: prohibited practices

    Editorially reviewed | control, prohibited-practices

  49. ControlApplicablev1.0.03 relations

    Quarterly sampling of live disclosures and markings in production

    praxikon:eu:ai-act:control:article-50-production-sampling

    Each quarter, sample the systems carrying an Article 50 scenario and verify in the production environment that the disclosure still appears and the marking is still present in the actual output, recording finding, owner and remediation deadline.

    Hangs off: Article 50: transparency

    Editorially reviewed | transparency

  50. Controlv1.0.04 relations

    Pre-release transparency check

    praxikon:eu:ai-act:control:article-50-release-check

    Before release, test that the applicable disclosure, marking or label is timely, clear and technically effective.

    Hangs off: Article 50: transparency

    Editorially reviewed | control, transparency

  51. ControlApplicablev1.0.04 relations

    Oversight during the test, incident reporting and recall procedure

    praxikon:eu:ai-act:control:article-60-oversight-and-incident-response

    The market surveillance authority may inspect unannounced. On a serious incident you report, take immediate mitigation or suspend, and you must have a procedure in place in advance for prompt recall of the system.

    Hangs off: Article 60: testing in real world conditions outside a sandbox

    Editorially reviewed | innovation

  52. Controlv1.0.04 relations

    Signal-to-action loop

    praxikon:eu:ai-act:control:article-72-post-market-monitoring-control

    Ensure real-world signals (deviations, complaints, incidents) demonstrably lead to analysis and, where needed, measures.

    Hangs off: Article 72: post-market monitoring

    Editorially reviewed | control, post-market

  53. Controlv1.0.04 relations

    Incident drill and deadline watch

    praxikon:eu:ai-act:control:article-73-incident-reporting-control

    Periodically test whether an incident can be reported within the legal deadlines, including the deployer-to-provider chain.

    Hangs off: Article 73: serious incident reporting

    Editorially reviewed | control, post-market

  54. Controlv1.0.04 relations

    Reassessment on substantial modification

    praxikon:eu:ai-act:control:conformity-ce-registration-control

    Rerun the conformity route whenever the system is substantially modified.

    Hangs off: Articles 43-49: conformity assessment, CE and registration

    Editorially reviewed | conformity, control

  55. ControlUpcomingv1.0.04 relations

    Suspension and incident notification control

    praxikon:eu:ai-act:control:deployer-suspension-and-incident-control

    A fixed rule that suspends use and notifies in the correct order as soon as you have reason to consider the system presents a risk or as soon as you identify a serious incident.

    Hangs off: Article 26: obligations of deployers of high-risk AI systems

    Editorially reviewed | high-risk-requirements

  56. ControlApplicablev1.0.05 relations

    Routing and deadline tracking of a request for an explanation

    praxikon:eu:ai-act:control:explanation-request-routing

    The control that ensures an incoming request reaches an identifiable person within a set period and is answered, instead of sitting in a general inbox.

    Hangs off: Article 85: right to lodge a complaint with the market surveillance authority, Article 86: right to an explanation of a decision

    Editorially reviewed | fundamental-rights

  57. ControlUpcomingv1.0.04 relations

    Currency check on the FRIA elements during use

    praxikon:eu:ai-act:control:fria-in-use-currency-check

    Periodically and on every change in process, duration of use, affected groups, risks or oversight measures, check whether the recorded elements still hold, and update the information as soon as they do not.

    Hangs off: Article 27: FRIA

    Editorially reviewed | fundamental-rights

  58. Controlv1.0.05 relations

    Pre-deployment FRIA go/no-go

    praxikon:eu:ai-act:control:fria-pre-deployment-gate

    Block deployment until applicability, assessment, mitigation and notification have been completed.

    Hangs off: Article 27: FRIA

    Editorially reviewed | control, fundamental-rights

  59. Controlv1.0.04 relations

    Role reassessment on every change

    praxikon:eu:ai-act:control:value-chain-representative-control

    Repeat the role assessment on every rebranding, modification or new use of an existing system.

    Hangs off: Articles 22-25: value chain and authorised representative

    Editorially reviewed | control, value-chain

  60. DefinitionIn forcev1.0.02 relations

    Notifying authority

    praxikon:eu:ai-act:definition:definitie-aanmeldende-autoriteit

    The national authority responsible for setting up and carrying out the procedures for assessing, designating and notifying conformity assessment bodies, and for monitoring them.

    Placed against the official source | definitions

  61. DefinitionIn forcev1.0.02 relations

    AI Office

    praxikon:eu:ai-act:definition:definitie-ai-bureau

    Not a standalone authority but a function within the European Commission. For general-purpose AI models the AI Office is your supervisor; for ordinary AI systems it is not.

    Placed against the official source | definitions

  62. DefinitionIn forcev1.0.02 relations

    AI literacy

    praxikon:eu:ai-act:definition:definitie-ai-geletterdheid

    Skills, knowledge and understanding that enable providers, deployers and affected persons to deploy AI systems in an informed way and to become aware of the opportunities, risks and possible harm of AI.

    Placed against the official source | definitions

  63. DefinitionIn forcev1.0.03 relations

    General-purpose AI model (GPAI model)

    praxikon:eu:ai-act:definition:definitie-ai-model-voor-algemene-doeleinden

    The model is not the system, and that distinction determines which chapter of obligations applies to you.

    Placed against the official source | definitions

  64. DefinitionIn forcev1.0.02 relations

    AI system

    praxikon:eu:ai-act:definition:definitie-ai-systeem

    The gateway definition of the Regulation's system track: if your application falls outside it, the obligations for AI systems do not apply. General-purpose AI models run on a separate track under Article 3(63), with their own obligations in Article 53.

    Placed against the official source | definitions

  65. DefinitionIn forcev1.0.02 relations

    Intended purpose

    praxikon:eu:ai-act:definition:definitie-beoogd-doel

    The use set by the provider on which the entire risk classification and assessment rest.

    Placed against the official source | definitions

  66. DefinitionIn forcev1.0.02 relations

    Special categories of personal data

    praxikon:eu:ai-act:definition:definitie-bijzondere-categorieen-persoonsgegevens

    The sensitive data categories from the GDPR and related European rules, imported here because the AI Act attaches both a prohibition and a narrow exception to them.

    Placed against the official source | definitions

  67. DefinitionIn forcev1.0.02 relations

    Biometric data

    praxikon:eu:ai-act:definition:definitie-biometrische-gegevens

    The AI Act uses its own, broader wording than the GDPR, and that difference decides whether you land in Annex III or Article 5.

    Placed against the official source | definitions

  68. DefinitionIn forcev1.0.03 relations

    Biometric identification

    praxikon:eu:ai-act:definition:definitie-biometrische-identificatie

    A one-to-many comparison against a database, to be distinguished from the one-to-one verification of point 36.

    Placed against the official source | definitions

  69. DefinitionIn forcev1.0.02 relations

    Post-remote biometric identification system

    praxikon:eu:ai-act:definition:definitie-biometrische-identificatie-op-afstand-achteraf

    The residual category: any remote identification that is not real-time. Not prohibited, but high-risk, and subject to its own authorisation regime in law enforcement.

    Placed against the official source | definitions

  70. DefinitionIn forcev1.0.02 relations

    Real-time remote biometric identification system

    praxikon:eu:ai-act:definition:definitie-biometrische-identificatie-op-afstand-in-real-time

    Remote identification where capture, comparison and identification happen without significant delay. The legislator explicitly closed the escape route of an artificial delay.

    Placed against the official source | definitions

  71. DefinitionIn forcev1.0.02 relations

    Deep fake

    praxikon:eu:ai-act:definition:definitie-deepfake

    Far broader than fake videos of famous people: objects, places, entities and events are covered too.

    Placed against the official source | definitions

  72. DefinitionIn forcev1.0.02 relations

    Downstream provider

    praxikon:eu:ai-act:definition:definitie-downstreamaanbieder

    A provider of an AI system, including a general-purpose AI system, which integrates an AI model, regardless of whether that model is provided by themselves and vertically integrated or obtained from another entity on a contractual basis.

    Placed against the official source | definitions

  73. DefinitionIn forcev1.0.02 relations

    Emotion recognition system

    praxikon:eu:ai-act:definition:definitie-emotieherkenningssysteem

    Prohibited in the workplace and in education since 2 February 2025; elsewhere an information duty under Article 50 applies since 2 August 2026.

    Placed against the official source | definitions

  74. DefinitionIn forcev1.0.02 relations

    Serious incident

    praxikon:eu:ai-act:definition:definitie-ernstig-incident

    Four categories of consequence, one of which is an infringement of fundamental rights protection. No physical harm is needed before a notification duty arises.

    Placed against the official source | definitions

  75. DefinitionIn forcev1.0.02 relations

    Instructions for use

    praxikon:eu:ai-act:definition:definitie-gebruiksinstructies

    The information the provider supplies to inform the deployer about, in particular, the intended purpose and proper use of an AI system. It is the hinge between the provider's obligations and the deployer's.

    Placed against the official source | definitions

  76. DefinitionIn forcev1.0.04 relations

    Deployer

    praxikon:eu:ai-act:definition:definitie-gebruiksverantwoordelijke

    The role that virtually every organisation buying and using AI ends up in.

    Placed against the official source | definitions

  77. DefinitionIn forcev1.0.02 relations

    Putting into service

    praxikon:eu:ai-act:definition:definitie-in-gebruik-stellen

    The concept that brings internally built systems which are never sold within the scope of the Regulation.

    Placed against the official source | definitions

  78. DefinitionIn forcev1.0.02 relations

    Input data

    praxikon:eu:ai-act:definition:definitie-inputdata

    The data entering the system or acquired by it, on the basis of which it produces its output. This is the data definition that touches the deployer, not just the provider.

    Placed against the official source | definitions

  79. DefinitionIn forcev1.0.02 relations

    Critical infrastructure

    praxikon:eu:ai-act:definition:definitie-kritieke-infrastructuur

    Critical infrastructure as defined in Article 2, point (4), of Directive (EU) 2022/2557, the CER Directive. The AI Act gives no definition of its own here but aligns with that framework.

    Placed against the official source | definitions

  80. DefinitionIn forcev1.0.02 relations

    Market surveillance authority

    praxikon:eu:ai-act:definition:definitie-markttoezichtautoriteit

    The national supervisor that enforces the AI Act on the market, with the powers from the general market surveillance regulation. This is the party that comes knocking and requests your documentation.

    Placed against the official source | definitions

  81. DefinitionIn forcev1.0.02 relations

    National competent authority

    praxikon:eu:ai-act:definition:definitie-nationale-bevoegde-autoriteit

    An umbrella term for two very different roles: the notifying authority and the market surveillance authority. For EU institutions the European Data Protection Supervisor takes their place.

    Placed against the official source | definitions

  82. DefinitionIn forcev1.0.02 relations

    Non-personal data

    praxikon:eu:ai-act:definition:definitie-niet-persoonsgebonden-gegevens

    Everything that is not personal data. The category exists to make clear that the AI Act applies even when no personal data is involved.

    Placed against the official source | definitions

  83. DefinitionIn forcev1.0.01 relations

    Publicly accessible space

    praxikon:eu:ai-act:definition:definitie-openbare-ruimte

    Any physical place, publicly or privately owned, accessible to an undetermined number of people. Access conditions and capacity limits are irrelevant.

    Placed against the official source | definitions

  84. DefinitionIn forcev1.0.05 relations

    Operator

    praxikon:eu:ai-act:definition:definitie-operator

    The umbrella term for all six roles in the chain, and not the person operating the controls.

    Placed against the official source | definitions

  85. DefinitionIn forcev1.0.02 relations

    Personal data

    praxikon:eu:ai-act:definition:definitie-persoonsgegevens

    The AI Act deliberately creates no separate concept here and refers to the GDPR. Your GDPR records and your AI Act file must therefore cover the same data.

    Placed against the official source | definitions

  86. DefinitionIn forcev1.0.02 relations

    Performance of an AI system

    praxikon:eu:ai-act:definition:definitie-prestaties-ai-systeem

    The ability of an AI system to achieve its intended purpose. Performance is therefore measured against the intended purpose, not against a standalone technical score.

    Placed against the official source | definitions

  87. DefinitionIn forcev1.0.02 relations

    Profiling

    praxikon:eu:ai-act:definition:definitie-profilering

    Taken from the GDPR, but decisive in the AI Act: an Annex III system that profiles always remains high-risk.

    Placed against the official source | definitions

  88. DefinitionIn forcev1.0.02 relations

    Law enforcement

    praxikon:eu:ai-act:definition:definitie-rechtshandhaving

    The activity, not the authority. Work carried out on behalf of a law enforcement authority is covered as well, including where a private party performs it.

    Placed against the official source | definitions

  89. DefinitionIn forcev1.0.01 relations

    Law enforcement authority

    praxikon:eu:ai-act:definition:definitie-rechtshandhavingsinstantie

    Not just the police and prosecution service. Also any other body entrusted under national law with public authority for detection, prosecution or public security.

    Placed against the official source | definitions

  90. DefinitionIn forcev1.0.02 relations

    Reasonably foreseeable misuse

    praxikon:eu:ai-act:definition:definitie-redelijkerwijs-te-voorzien-misbruik

    Use outside the intended purpose that the provider could have seen coming, and must therefore anticipate.

    Placed against the official source | definitions

  91. DefinitionIn forcev1.0.02 relations

    Risk

    praxikon:eu:ai-act:definition:definitie-risico

    Risk is the combination of the probability of harm occurring and the severity of that harm. It is the unit of measurement underpinning the entire regulation, from prohibited practices to the Article 9 risk management system.

    Placed against the official source | definitions

  92. DefinitionIn forcev1.0.02 relations

    Substantial modification

    praxikon:eu:ai-act:definition:definitie-substantiele-wijziging

    A change to an AI system after it has been placed on the market or put into service that the provider did not foresee in the initial conformity assessment, and that affects compliance with Chapter III, Section 2 or changes the intended purpose.

    Placed against the official source | definitions

  93. DefinitionIn forcev1.0.02 relations

    Biometric categorisation system

    praxikon:eu:ai-act:definition:definitie-systeem-voor-biometrische-categorisering

    An AI system that assigns people to categories on the basis of their biometric data. The carve-out for functions ancillary to another commercial service is narrow and is routinely read far too broadly in practice.

    Placed against the official source | definitions

  94. DefinitionIn forcev1.0.02 relations

    Remote biometric identification system

    praxikon:eu:ai-act:definition:definitie-systeem-voor-biometrische-identificatie-op-afstand

    An AI system that identifies people without their active involvement, typically at a distance, by comparing them against a reference database. The decisive words are "active involvement".

    Placed against the official source | definitions

  95. DefinitionIn forcev1.0.03 relations

    Systemic risk

    praxikon:eu:ai-act:definition:definitie-systeemrisico

    A concept that applies exclusively to GPAI models, and that is unrelated to the high-risk classification of AI systems.

    Placed against the official source | definitions

  96. DefinitionIn forcev1.0.02 relations

    Recall of an AI system

    praxikon:eu:ai-act:definition:definitie-terugroepen-ai-systeem

    A measure aimed at returning an AI system to the provider, taking it out of service, or disabling its use, where that system has already been made available to deployers. A recall reaches systems already in use.

    Placed against the official source | definitions

  97. DefinitionIn forcev1.0.02 relations

    Testing in real-world conditions

    praxikon:eu:ai-act:definition:definitie-testen-onder-reele-omstandigheden

    Temporarily testing an AI system for its intended purpose outside the lab, in order to gather reliable data and assess conformity. It does not count as placing on the market or putting into service, provided you meet all conditions of Article 57 or 60.

    Placed against the official source | definitions

  98. DefinitionIn forcev1.0.02 relations

    Sandbox plan

    praxikon:eu:ai-act:definition:definitie-testomgevingsplan

    The agreement between you and the supervisory authority about what you will do in an AI regulatory sandbox: objectives, conditions, timeframe, methodology and requirements. It is a two-sided document, not an internal plan.

    Placed against the official source | definitions

  99. DefinitionIn forcev1.0.02 relations

    Safety component

    praxikon:eu:ai-act:definition:definitie-veiligheidscomponent

    One of the two routes into the high-risk classification of Article 6(1), and often overlooked outside manufacturing.

    Placed against the official source | definitions

  100. DefinitionIn forcev1.0.03 relations

    Widespread infringement

    praxikon:eu:ai-act:definition:definitie-wijdverbreide-inbreuk

    An act or omission contrary to Union law protecting the interests of individuals that harms the collective interests of persons in at least two other Member States, or that, with common features, occurs concurrently and is committed by the same operator in at least three Member States.

    Placed against the official source | definitions

  101. DefinitionIn forcev1.0.02 relations

    Floating-point operation (FLOP)

    praxikon:eu:ai-act:definition:definitie-zwevendekommabewerking-flop

    Any mathematical operation or assignment involving floating-point numbers. This is the unit of computation with which the Regulation measures the scale of training of a general-purpose AI model.

    Placed against the official source | definitions

  102. Evidencev1.0.05 relations

    Article 6 and Annex III classification record

    praxikon:eu:ai-act:evidence:annex-iii-classification-record

    Traceable rationale covering intended purpose, Annex III category, Article 6(3) assessment and registration decision.

    Hangs off: Annex III: high-risk AI

    Editorially reviewed | evidence, high-risk

  103. Evidencev1.0.04 relations

    Data governance file

    praxikon:eu:ai-act:evidence:article-10-data-governance-record

    Record per dataset of origin, choices, assumptions, bias examination and mitigations.

    Hangs off: Article 10: data and data governance

    Editorially reviewed | evidence, high-risk-requirements

  104. Evidencev1.0.04 relations

    Logs and retention regime

    praxikon:eu:ai-act:evidence:article-12-logging-record

    Log files with a retention period appropriate to the purpose and at least six months for deployers (Articles 19 and 26).

    Hangs off: Article 12: logging and traceability

    Editorially reviewed | evidence, high-risk-requirements

  105. Evidencev1.0.04 relations

    Instructions and interpretation file

    praxikon:eu:ai-act:evidence:article-13-instructions-record

    The received instructions for use plus their internal translation into work instructions per role.

    Hangs off: Article 13: transparency towards deployers

    Editorially reviewed | evidence, high-risk-requirements

  106. Evidencev1.0.04 relations

    Oversight file per system

    praxikon:eu:ai-act:evidence:article-14-human-oversight-record

    Record of oversight measures, appointed persons, their training and the moments of intervention.

    Hangs off: Article 14: human oversight

    Editorially reviewed | evidence, high-risk-requirements

  107. Evidencev1.0.05 relations

    AI literacy measures record

    praxikon:eu:ai-act:evidence:article-4-measures-record

    Versioned record of roles, context, measures, participation or instruction and review moments.

    Hangs off: Article 4: AI literacy

    Editorially reviewed | ai-literacy, evidence

  108. EvidenceApplicablev1.0.03 relations

    Register of participation and instruction per person, system and date

    praxikon:eu:ai-act:evidence:article-4-participation-register

    Internal register showing who received which instruction, working session, training or guidance, for which system, on which date and on what basis, including new joiners, contractors and external staff.

    Hangs off: Article 4: AI literacy

    Editorially reviewed | ai-literacy

  109. EvidenceApplicablev1.0.03 relations

    Role-system matrix with the established literacy need

    praxikon:eu:ai-act:evidence:article-4-role-system-matrix-record

    The recorded matrix of roles against AI systems, with the context of use, affected persons, risk and selected measure per combination, dated and with an owner per row.

    Hangs off: Article 4: AI literacy

    Editorially reviewed | ai-literacy

  110. Evidencev1.0.04 relations

    Article 5 screening record

    praxikon:eu:ai-act:evidence:article-5-screening-record

    A record per system that the Article 5 screening was performed, with outcome and reasoning. The conclusion "no prohibited practice" is evidence too.

    Hangs off: Article 5: prohibited practices

    Editorially reviewed | evidence, prohibited-practices

  111. EvidenceApplicablev1.0.03 relations

    Test report per touchpoint: disclosure visible, timely and accessible

    praxikon:eu:ai-act:evidence:article-50-disclosure-test-report

    Dated record per interface and channel showing that the disclosure appears at the latest at first interaction or exposure, is clear and distinguishable, and passed the accessibility check, with screenshot, version number and tester identity.

    Hangs off: Article 50: transparency

    Editorially reviewed | transparency

  112. Evidencev1.0.05 relations

    Transparency implementation record

    praxikon:eu:ai-act:evidence:article-50-implementation-record

    Record of scenario, actor, disclosure or marking, technical implementation, test and owner.

    Hangs off: Article 50: transparency

    Editorially reviewed | evidence, transparency

  113. EvidenceApplicablev1.0.03 relations

    Supplier statement on machine-readable marking of output

    praxikon:eu:ai-act:evidence:article-50-supplier-marking-statement

    Written statement from the supplier describing which marking is applied to the output, in which machine-readable format, how robust and interoperable the solution is, and whether the marking survives editing or export.

    Hangs off: Article 50: transparency

    Editorially reviewed | transparency

  114. EvidenceApplicablev1.0.04 relations

    Dated and documented informed consent of test subjects

    praxikon:eu:ai-act:evidence:article-61-informed-consent-record

    For every test subject you record freely given informed consent, covering five prescribed information elements, dated, documented, with a copy provided to the subject.

    Hangs off: Article 60: testing in real world conditions outside a sandbox

    Editorially reviewed | innovation

  115. Evidencev1.0.04 relations

    Monitoring plan and reports

    praxikon:eu:ai-act:evidence:article-72-post-market-monitoring-record

    The plan as part of the technical documentation plus the periodic analyses and follow-up actions.

    Hangs off: Article 72: post-market monitoring

    Editorially reviewed | evidence, post-market

  116. Evidencev1.0.04 relations

    Incident register and reports

    praxikon:eu:ai-act:evidence:article-73-incident-reporting-record

    Record of incidents, analyses, reports to supervisors and corrective measures.

    Hangs off: Article 73: serious incident reporting

    Editorially reviewed | evidence, post-market

  117. Evidencev1.0.04 relations

    Conformity file

    praxikon:eu:ai-act:evidence:conformity-ce-registration-record

    The assessment, EU declaration of conformity, CE marking and registration proof, per system version.

    Hangs off: Articles 43-49: conformity assessment, CE and registration

    Editorially reviewed | conformity, evidence

  118. EvidenceUpcomingv1.0.04 relations

    Deployment dossier: logs, worker information and information to affected persons

    praxikon:eu:ai-act:evidence:deployer-use-dossier

    The dossier that shows you retain the logs, that you informed workers and their representatives in time, and that the people about whom decisions are made are aware of it.

    Hangs off: Article 26: obligations of deployers of high-risk AI systems

    Editorially reviewed | high-risk-requirements

  119. EvidenceApplicablev1.0.05 relations

    Register of requests for an explanation

    praxikon:eu:ai-act:evidence:explanation-request-record

    Per request: who made it, about which decision, which system and which version contributed to it, what explanation was given and when. This is also the file that shows you did not silently ignore the right.

    Hangs off: Article 85: right to lodge a complaint with the market surveillance authority, Article 86: right to an explanation of a decision

    Editorially reviewed | fundamental-rights

  120. EvidenceUpcomingv1.0.04 relations

    Notification to the market surveillance authority with the completed template

    praxikon:eu:ai-act:evidence:fria-authority-notification

    The sent notification through which you report the assessment results to the market surveillance authority, with the completed template attached, plus date of dispatch and acknowledgement of receipt.

    Hangs off: Article 27: FRIA

    Editorially reviewed | fundamental-rights

  121. EvidenceUpcomingv1.0.04 relations

    Crosswalk showing the FRIA complements rather than repeats the DPIA

    praxikon:eu:ai-act:evidence:fria-dpia-crosswalk

    An overview indicating per Article 27(1) element whether it is already covered in the data protection impact assessment and where, so it is visible which elements exist only in the FRIA.

    Hangs off: Article 27: FRIA

    Editorially reviewed | fundamental-rights

  122. Evidencev1.0.06 relations

    FRIA report and notification

    praxikon:eu:ai-act:evidence:fria-report

    Dated impact assessment, measures, residual risks and, where required, notification to the market surveillance authority.

    Hangs off: Article 27: FRIA

    Editorially reviewed | evidence, fundamental-rights

  123. Evidencev1.0.04 relations

    Value-chain file

    praxikon:eu:ai-act:evidence:value-chain-representative-record

    Record per system of role, contractual arrangements on information and cooperation, and the appointment of a representative where required.

    Hangs off: Articles 22-25: value chain and authorised representative

    Editorially reviewed | evidence, value-chain

  124. ExampleGuidancev1.0.03 relations

    Candidate recommendation that automatically becomes a decision

    praxikon:eu:ai-act:example:example-aanbeveling-wordt-besluit-werving

    An employer uses a system that ranks applicants and recommends a candidate to hire. In one setup a recruiter weighs that recommendation in their own assessment; in the other the outcome is applied automatically and a candidate is rejected without anyone looking at it.

    Hangs off: Annex III: high-risk AI

    Placed against the official source | examples

  125. ExampleGuidancev1.0.02 relations

    AI articles on EU policy without substantive review

    praxikon:eu:ai-act:example:example-ai-artikelen-zonder-menselijke-toetsing

    A website automatically publishes AI-generated articles about European policy. There is an editorial charter on paper, but nobody reviews the substance. Before publication only a spell check runs, and a second AI model reviews the text.

    Hangs off: Article 50: transparency

    Placed against the official source | examples

  126. ExampleGuidancev1.0.02 relations

    AI summary of a council decision under editorial control

    praxikon:eu:ai-act:example:example-ai-samenvatting-onder-eindredactie

    A news site places an AI-generated summary beneath a journalist's article about a recent town council decision. The editor in chief reads the summary on substance, checks the facts and signs off for publication.

    Hangs off: Article 50: transparency

    Placed against the official source | examples

  127. ExampleEditorialv1.0.03 relations

    Facial recognition at access control: the guard behind the camera counts too

    praxikon:eu:ai-act:example:example-artikel-4-gezichtsherkenning-toegangscontrole

    An organisation secures the entrances to its buildings with facial recognition and uses that biometric access control to register visitors as well. When the system returns no match, a security officer reviews the camera images and decides personally whether someone may enter. The question is whose measures have to reach that officer: those of the supplier of the model, those of the department that deploys the system, or both.

    Hangs off: Article 4: AI literacy

    Placed against the official source | examples

  128. ExampleEditorialv1.0.03 relations

    Police using AI in investigations: context sets how deep the training goes

    praxikon:eu:ai-act:example:example-artikel-4-politie-opsporingsanalyse

    A police force uses AI to search large volumes of investigation files and surface connections a detective would otherwise miss. The outputs feed into the choice of which suspect is pursued further and end up in documents that enter the criminal process. The question is whether one and the same basic instruction is enough for the analyst operating the model and for the detective who acts on its output.

    Hangs off: Article 4: AI literacy

    Placed against the official source | examples

  129. ExampleEditorialv1.0.02 relations

    Newsroom with generative AI: do freelancers count within your measures?

    praxikon:eu:ai-act:example:example-artikel-4-redactie-generatieve-content

    A newsroom uses generative AI to prepare summaries, headlines and imagery, after which an editor finishes the piece and the desk decides to publish. Part of that work sits with freelancers, and an outside agency produces marketing content with the same tools. The question is whether your AI literacy measures must reach those freelancers and that agency, or only the people on the payroll.

    Hangs off: Article 4: AI literacy

    Placed against the official source | examples

  130. ExampleEditorialv1.0.03 relations

    AI chat in recruitment and selection: what the applicant must be told

    praxikon:eu:ai-act:example:example-artikel-50-ai-chat-sollicitanten

    A recruiter deploys an AI chat that puts candidates through a first screening conversation after they respond to a job posting, and adds their answers to their CV. The chat introduces itself with a first name and writes in a casual conversational tone. The question is whether these applicants reasonably realise that they are talking to an AI system.

    Hangs off: Article 50: transparency

    Placed against the official source | examples

  131. ExampleGuidancev1.0.03 relations

    Camera at the entrance: access control versus biometric categorisation

    praxikon:eu:ai-act:example:example-artikel-50-camera-toegangscontrole-categorisatie

    An organisation admits staff through facial recognition at its access control gate and additionally runs a camera in the visitor area that sorts faces into age groups. Both applications run on the same biometric infrastructure and the same images. The question is which of the two requires the people involved to be actively informed.

    Hangs off: Article 50: transparency

    Placed against the official source | examples

  132. ExampleGuidancev1.0.03 relations

    Code assistant for developers: an exception, until it faces outward

    praxikon:eu:ai-act:example:example-artikel-50-code-assistent

    A software company uses an AI assistant for code suggestions and code review, available only to professional developers. The same company also runs a helpdesk chatbot for customers.

    Hangs off: Article 50: transparency

    Placed against the official source | examples

  133. ExampleGuidancev1.0.03 relations

    Fraud reporting portal at a bank: why the law enforcement exception drops out

    praxikon:eu:ai-act:example:example-artikel-50-fraudemeldportaal-bank

    A bank opens an AI-driven reporting portal where customers can flag suspected fraud around their payment account or loan. The system asks follow-up questions, categorises the report and routes it to fraud detection and, where money laundering signals appear, to the internal reporting team. Because the portal concerns criminal offences, the bank assumes the disclosure duty for direct AI interaction does not apply.

    Hangs off: Article 50: transparency

    Placed against the official source | examples

  134. ExampleGuidancev1.0.03 relations

    AI text from a municipality: when a final check counts as editorial control

    praxikon:eu:ai-act:example:example-artikel-50-gemeentelijke-ai-tekst

    A municipality has an AI system write the web pages about a changed scheme for social assistance and allowances, meant to explain to citizens what they are entitled to. A communications officer reads the text for style and spelling and publishes it. The question is whether this public service thereby falls under the exception to the labelling duty.

    Hangs off: Article 50: transparency

    Placed against the official source | examples

  135. ExampleGuidancev1.0.02 relations

    Internal assistant for HR and compliance: an exception with a condition

    praxikon:eu:ai-act:example:example-artikel-50-interne-medewerkersassistent

    An organisation gives staff an internal AI assistant for HR, legal, procurement, compliance and IT questions. Must that assistant disclose at every turn that it is AI?

    Hangs off: Article 50: transparency

    Placed against the official source | examples

  136. ExampleGuidancev1.0.02 relations

    Diagnostic support for clinicians: no disclosure duty, still due care

    praxikon:eu:ai-act:example:example-artikel-50-klinisch-beslissysteem

    A hospital deploys an interactive AI system used exclusively by properly trained health professionals to support medical diagnosis and suggest treatments. The question is whether the patient or the clinician must be told it is AI.

    Hangs off: Article 50: transparency

    Placed against the official source | examples

  137. ExampleGuidancev1.0.03 relations

    Law enforcement: exempt from the disclosure duty, with safeguards

    praxikon:eu:ai-act:example:example-artikel-50-opsporing-uitzondering

    An authority empowered by law to detect criminal offences wants to deploy an interactive AI system without telling those involved that they are communicating with AI.

    Hangs off: Article 50: transparency

    Placed against the official source | examples

  138. ExampleGuidancev1.0.03 relations

    An induction call with the customer at the moment of go-live

    praxikon:eu:ai-act:example:example-asimov-inductiecall-bij-klant

    Asimov AI is a micro organisation of at most fifteen people that supplies AI services for legislative work to government institutions and companies. With every new contract it holds one or more induction calls with the team leads and officials who will use the platform, explaining how the platform and the underlying models work and how hallucinations arise in this domain and can be mitigated.

    Hangs off: Article 4: AI literacy

    Placed against the official source | examples

  139. ExampleEditorialv1.0.03 relations

    Performance scoring for staff goes wrong: report or not

    praxikon:eu:ai-act:example:example-beoordelingssysteem-personeel-incidentmelding

    An employer uses an AI system that scores employee performance and lets that score weigh in promotion and dismissal. After a change to the model it turns out that a group of staff was scored too low for months, and decisions have already been taken on those scores. HR wonders whether this is a serious incident and who would have to report it.

    Hangs off: Article 73: serious incident reporting

    Placed against the official source | examples

  140. ExampleGuidancev1.0.02 relations

    Face comparison at the border gate: verification or identification

    praxikon:eu:ai-act:example:example-biometrische-verificatie-grenspoort

    An automated border gate uses biometric facial recognition to compare a traveller’s face with the photo in the passport chip. The same camera could technically also compare against a law-enforcement database, and exactly that difference decides whether this biometrics is high-risk.

    Hangs off: Annex III: high-risk AI

    Placed against the official source | examples

  141. ExampleGuidancev1.0.03 relations

    A three-part training for legal and public affairs staff

    praxikon:eu:ai-act:example:example-booking-training-voor-juristen

    Booking.com built a three-part training for its legal and public affairs teams: first basic terminology and the difference between classic machine learning and language models, then how AI works inside the company, then the regulatory landscape and where it meets the law they already practise. The material was also released as a video and podcast series with subtitles and written handouts.

    Hangs off: Article 4: AI literacy

    Placed against the official source | examples

  142. ExampleGuidancev1.0.02 relations

    Call centre measures employees' anger

    praxikon:eu:ai-act:example:example-callcenter-emotieherkenning-medewerkers

    A call centre uses webcams and voice recognition to track employees' emotions, such as anger. The same company also uses voice analysis to detect when a customer becomes irritated.

    Hangs off: Article 5: prohibited practices

    Placed against the official source | examples

  143. ExampleGuidancev1.0.03 relations

    A CV filter that ranks applicants

    praxikon:eu:ai-act:example:example-cv-filter-rangschikt-sollicitanten

    An employer has an external recruitment system score and rank every incoming application, after which recruiters only review the top twenty percent by hand. The vendor puts the system on the market under its own name, and the employer uses it in its own selection process.

    Hangs off: Annex III: high-risk AI

    Placed against the official source | examples

  144. ExampleGuidancev1.0.02 relations

    Database query and standard spreadsheet without AI features

    praxikon:eu:ai-act:example:example-databasequery-en-standaard-spreadsheet

    A customer service department runs a database query to find all customers who purchased a specific product last month, and calculates the average from a satisfaction survey in a standard spreadsheet. Every step follows predefined instructions.

    Hangs off: Article 4: AI literacy

    Placed against the official source | examples

  145. ExampleGuidancev1.0.03 relations

    Lawyers learn the technology, developers learn the law

    praxikon:eu:ai-act:example:example-dedalus-gekruiste-training

    Dedalus Healthcare, which among other things supplies AI that predicts complications for hospital patients, trains its legal staff, data protection officer, compliance function and quality and regulatory affairs department on the technical side. Developers and engineers conversely receive training focused on the legal and compliance aspects of the AI Act. The executive committee received its own session tailored to its role.

    Hangs off: Article 4: AI literacy

    Placed against the official source | examples

  146. ExampleGuidancev1.0.03 relations

    Deep fake on a Christmas card: the provider marks, the private person does not

    praxikon:eu:ai-act:example:example-deepfake-op-een-kerstkaart

    A private individual uses a generative AI service to create a deep fake of themselves and their household for their own Christmas card, purely personal and with no business purpose.

    Hangs off: Article 50: transparency

    Placed against the official source | examples

  147. ExampleGuidancev1.0.02 relations

    A real car against an AI background is not a deep fake

    praxikon:eu:ai-act:example:example-echt-product-tegen-ai-achtergrond

    A car company photographs an existing model and places it in an advertisement against a fully AI-generated background with an invented landscape. The car itself is untouched.

    Hangs off: Article 50: transparency

    Placed against the official source | examples

  148. ExampleGuidancev1.0.02 relations

    Medical exception: accessibility yes, burnout detection no

    praxikon:eu:ai-act:example:example-emotieherkenning-medische-uitzondering

    An employer wants to deploy emotion recognition. In one scenario the system assists employees with autism and improves accessibility for blind and deaf colleagues. In the other it measures stress levels to flag burnout, boredom or loss of motivation.

    Hangs off: Article 5: prohibited practices

    Placed against the official source | examples

  149. ExampleEditorialv1.0.03 relations

    Serious incident on the production line: who reports and within what deadline

    praxikon:eu:ai-act:example:example-ernstig-incident-productielijn-meldtermijn

    A manufacturer supplies an AI system that runs as a safety component in a machine on the production line and at the same time drives quality control. At a customer's factory an operator is seriously injured after the machine failed to stop on an anomaly. The question is who reports, to whom, and which clock is already running at that moment.

    Hangs off: Article 73: serious incident reporting

    Placed against the official source | examples

  150. ExampleGuidancev1.0.02 relations

    Expert system that draws a conclusion from encoded knowledge

    praxikon:eu:ai-act:example:example-expertsysteem-medische-diagnose

    A hospital uses an older diagnostic support expert system in which physicians encoded knowledge, facts and rules. Based on the symptoms a doctor enters, the system independently draws a conclusion about possible conditions.

    Hangs off: Article 4: AI literacy

    Placed against the official source | examples

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.