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 342 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.14 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. ActionApplicablev1.0.04 relations

    Inform the test subject and obtain consent to participate

    praxikon:eu:ai-act:action:article-61-inform-and-obtain-consent

    Give every test subject concise, clear, relevant and understandable information beforehand on the five points of Article 61(1), then obtain freely-given informed consent, date and document that consent, and give a copy to the subject or the legal representative.

    Hangs off: Article 61: informed consent of test subjects for testing in real world conditions

    Editorially reviewed | fundamental-rights, innovation

  17. ActionEditorialv1.0.04 relations

    Make use of the SME facilities in Article 62

    praxikon:eu:ai-act:action:article-62-claim-sme-facilities

    Apply for priority access to the AI regulatory sandbox, use the national communication channel for questions about implementation, sign up for the standardisation process, and on a conformity assessment under Article 43 ask how the fee reduction has been applied.

    Hangs off: Article 62: measures for providers and deployers that are SMEs or start-ups

    Editorially reviewed | governance, innovation

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

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

  20. ActionEditorialv1.0.04 relations

    Scope a voluntary code of conduct and separate it from your duties

    praxikon:eu:ai-act:action:article-95-scope-a-voluntary-code

    Choose the paragraph 1 or the paragraph 2 route, name which requirements you apply voluntarily and which you do not, give the code clear objectives and key performance indicators, and keep the voluntary commitments administratively separate from the obligations that continue to apply in full.

    Hangs off: Article 95: codes of conduct for voluntary application of specific requirements

    Editorially reviewed | governance, innovation

  21. ActionEditorialv1.0.08 relations

    Assign to each obligation the penalty ceiling that belongs to it

    praxikon:eu:ai-act:action:article-99-101-map-penalty-tiers

    Walk through your obligations register and mark per line which ceiling applies: Article 99(3) for Article 5, Article 99(4) for the role duties enumerated there, Article 25(2) and (4) and Article 50, Article 99(5) for answering information requests, and otherwise the national penalty regime under Article 99(1). Add the Article 101 regime wherever you provide a general-purpose AI model yourself, and the Article 75c regime wherever the AI Office is competent.

    Hangs off: Article 99, 100 and 101: the penalty structure per obligation

    Editorially reviewed | enforcement, governance

  22. ActionUpcomingv1.0.04 relations

    Assess for every design change whether it is significant

    praxikon:eu:ai-act:action:assess-significant-design-change

    Fix a moment in your change and release process at which someone assesses and records whether an intended change to a legacy high-risk system is a significant change in its design, before the change goes into production.

    Hangs off: Article 111(2): legacy high-risk systems and the 2 August 2030 date

    Editorially reviewed | high-risk, timeline

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

  24. ActionUpcomingv1.0.04 relations

    Map every system to a point of Annex III

    praxikon:eu:ai-act:action:map-system-to-annex-iii-area

    Determine per AI system which of the eight areas and which lettered subpoint the intended purpose touches, or establish with reasons that no point applies. Then run the Article 6(3) test and record the outcome as Article 6(4) requires. Do so at the level of the intended purpose and not at the level of the department or the sector.

    Hangs off: Annex III: the eight areas separately

    Editorially reviewed | high-risk

  25. ActionEditorialv1.0.05 relations

    Mark and register what you submit to an authority or body

    praxikon:eu:ai-act:action:mark-confidential-material-on-submission

    State on every submission which part is confidential business information, trade secret or source code, keep track of what was handed to whom on what date, and on a further request ask about the necessity and the purpose within the meaning of Article 78(2).

    Hangs off: Article 78: confidentiality of what you submit to an authority

    Editorially reviewed | enforcement, governance

  26. ActionEditorialv1.0.04 relations

    Make sure a report about an AI system reaches your reporting channel

    praxikon:eu:ai-act:action:open-a-protected-reporting-route

    Only for organisations that must already have a reporting arrangement. Make visible in it that an infringement of the AI Regulation is a reportable infringement, designate who receives such a report, agree how the identity of the person reporting stays out of the rest of the process, and record whether you handle anonymous reports.

    Hangs off: Article 87: reporting of infringements and protection of reporting persons

    Editorially reviewed | fundamental-rights, governance

  27. ActionApplicablev1.0.04 relations

    Plan compliance for legacy public sector systems by 2 August 2030

    praxikon:eu:ai-act:action:plan-legacy-public-system-compliance

    Determine which high-risk systems are intended to be used by public authorities and were already running before the cut off date for their route, and count back from the conformity assessment and the registration to a plan that finishes before 2 August 2030.

    Hangs off: Article 111(2): legacy high-risk systems and the 2 August 2030 date

    Editorially reviewed | high-risk, timeline

  28. ActionEditorialv1.0.05 relations

    Prepare a derogation request and the exit plan that goes with it

    praxikon:eu:ai-act:action:prepare-article-46-derogation-request

    Write in advance the reasoning paragraph 1 calls for, with the exceptional reason invoked, the evidence that the system complies with the requirements of Section 2, the status of the ongoing conformity assessment, and an exit plan in case the authorisation is refused or withdrawn.

    Hangs off: Article 46: derogation from conformity assessment procedure

    Editorially reviewed | conformity, enforcement

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

  30. ActionApplicablev1.0.06 relations

    Justify and record your reliance on Article 4a

    praxikon:eu:ai-act:action:record-bias-testing-legal-basis

    Only for those who themselves decide to process special categories of personal data for bias testing. In that case record which paragraph of Article 4a you rely on and whether that paragraph is open to your role, why other data do not suffice, which safeguards apply, who has access and when the data are deleted. Replace old references to Article 10(5) while you are there.

    Hangs off: Article 4a: legal basis for bias testing with special categories of personal data

    Editorially reviewed | fundamental-rights, high-risk-requirements

  31. ActionApplicablev1.0.07 relations

    Register yourself and the system before it reaches the market or is put into service

    praxikon:eu:ai-act:action:register-in-eu-database-before-market-entry

    Determine per system which of the four Article 49 routes applies, the ordinary Annex III route, the Article 6(3) route, the secure section for law enforcement, migration, asylum and border control management, or the national route for point 2 of Annex III, and complete the registration before the system is placed on the market, put into service or used.

    Hangs off: Article 49: registration in the EU database before the system reaches the market

    Editorially reviewed | conformity, high-risk

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

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

  34. Actorv1.0.0348 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

  35. Actorv1.0.050 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

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

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

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

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

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

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

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

  43. ChangeGuidancev1.0.03 relations

    Transparency Code of Practice found adequate

    praxikon:eu:ai-act:change:2026-07-09-transparency-code-adequacy

    The Commission (8 July 2026) and the AI Board (9 July 2026) consider the code adequate for Article 50(2), (4) and (5).

    Hangs off: Article 50: transparency

    Placed against the official source | transparency

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

  45. ChangeIn forcev1.0.08 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

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

  47. ChangeIn forcev1.0.07 relations

    Article 4a inserted, Article 10(5) deleted

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

    Since 27 July 2026 the legal basis for bias detection using special categories of personal data sits as Article 4a in Chapter I and no longer as Article 10(5) in Chapter III. The circle has widened from providers of high-risk systems alone to providers and deployers of other AI systems and models and deployers of high-risk systems, on the same conditions.

    Hangs off: Article 4a: legal basis for bias testing with special categories of personal data

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

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

  49. ChangeGuidancev1.1.03 relations

    Guidelines on Article 50 formally adopted

    praxikon:eu:ai-act:change:2026-11-05-article-50-guidelines-adopted

    On 5 November 2026 the Commission adopted the guidelines as C(2026) 7702 final, also in Dutch; on 12 November 2026 they appeared in the Official Journal as Communication C/2026/6005. The content and the point numbering equal the text of 20 July 2026; the guidelines remain non-binding.

    Hangs off: Article 50: transparency

    Placed against the official source | transparency

  50. ChangeUpcomingv1.0.03 relations

    Rules for AI regulatory sandboxes adopted

    praxikon:eu:ai-act:change:2026-11-10-sandbox-implementing-regulation

    On 10 November 2026 the Commission adopted Implementing Regulation (EU) 2026/2487, in force from 1 December 2026. It governs application and selection, costs, the sandbox plan, the written proof and the exit report for all Article 57 AI regulatory sandboxes.

    Hangs off: Article 57: AI regulatory sandboxes

    Placed against the official source | innovation

  51. ControlUpcomingv1.0.04 relations

    Reassessment on a change of intended purpose

    praxikon:eu:ai-act:control:annex-iii-area-rescan-trigger

    The control that ensures a change of intended purpose, a new vendor feature, a new use inside the organisation or a delegated act under Article 7 triggers a fresh assessment of the mapping to a point of Annex III, instead of the first record standing for years while the system or the list moves.

    Hangs off: Annex III: the eight areas separately

    Editorially reviewed | high-risk

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

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

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

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

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

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

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

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

  60. ControlEditorialv1.0.05 relations

    Review of an authorisation expiring, being refused or withdrawn

    praxikon:eu:ai-act:control:article-46-derogation-exit-review

    The control that keeps a system running under Article 46 under watch: the ongoing conformity assessment has an owner and an end date, the fifteen calendar days of paragraph 4 are in the calendar, and a rehearsed plan is in place to stop use with immediate effect and discard all results and outputs if the authorisation is refused or withdrawn.

    Hangs off: Article 46: derogation from conformity assessment procedure

    Editorially reviewed | conformity, control, enforcement

  61. ControlApplicablev1.0.07 relations

    Release gate: no market entry without registration

    praxikon:eu:ai-act:control:article-49-pre-market-registration-gate

    The control that stops any Annex III system from being placed on the market, put into service or used before the registration is complete, with an explicit check on the Article 6(3) route and on the Article 26(8) question whether the provider entry is present in the database.

    Hangs off: Article 49: registration in the EU database before the system reaches the market

    Editorially reviewed | conformity, control, high-risk

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

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

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

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

  66. ControlEditorialv1.0.04 relations

    Consent and withdrawal review before a test in real world conditions starts

    praxikon:eu:ai-act:control:article-61-consent-and-withdrawal-review

    The control that no subject participates before the information pack is complete, the consent record is dated and a copy has been given, and that the withdrawal route with its recipient, period and deletion step works and has been rehearsed once.

    Hangs off: Article 61: informed consent of test subjects for testing in real world conditions

    Editorially reviewed | control, fundamental-rights, innovation

  67. ControlEditorialv1.0.04 relations

    Fee and access review on a conformity assessment

    praxikon:eu:ai-act:control:article-62-fee-and-access-review

    The control that on every application for a conformity assessment under Article 43 and on every sandbox application it is checked whether the SME facilities have been invoked and whether the proportionate fee reduction has been made visible, and that the answer reaches the procurement file.

    Hangs off: Article 62: measures for providers and deployers that are SMEs or start-ups

    Editorially reviewed | control, governance, innovation

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

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

  70. ControlEditorialv1.0.05 relations

    Review before handing over source code or trade secrets

    praxikon:eu:ai-act:control:article-78-disclosure-review

    The control that sends a submission touching source code, training methodology or trade secrets through a fixed review: is the request reasoned, what purpose was stated, which part is strictly necessary, and who inside the organisation signs off on it.

    Hangs off: Article 78: confidentiality of what you submit to an authority

    Editorially reviewed | control, enforcement, governance

  71. ControlEditorialv1.0.04 relations

    Review that keeps voluntary and mandatory apart

    praxikon:eu:ai-act:control:article-95-voluntary-versus-mandatory-review

    The control that no external statement, quotation, tender response or annual report presents a code of conduct as cover for an obligation under the Regulation, and that every voluntary commitment has an owner, an indicator and a moment of measurement before it goes out.

    Hangs off: Article 95: codes of conduct for voluntary application of specific requirements

    Editorially reviewed | control, governance, innovation

  72. ControlEditorialv1.0.08 relations

    Recording of the factors in Article 99(7)

    praxikon:eu:ai-act:control:article-99-101-mitigating-factor-record

    The control that ensures the factors which determine the amount of a fine are recorded at the time and not reconstructed afterwards: which technical and organisational measures were in place, when you notified an infringement yourself, how you responded to requests from the authority, and what you did to mitigate the harm suffered by affected persons. Those factors cut both ways, so the same record can also count against you; that is a reason to keep it properly rather than not at all.

    Hangs off: Article 99, 100 and 101: the penalty structure per obligation

    Editorially reviewed | control, enforcement

  73. ControlApplicablev1.0.05 relations

    Access and deletion control for bias testing

    praxikon:eu:ai-act:control:bias-testing-data-deletion

    The control that ensures the special categories stay with authorised people, are not transmitted, transferred or otherwise accessed by other parties, and are actually deleted once the bias has been corrected or the retention period ends, instead of lingering because nobody watches the deadline.

    Hangs off: Article 4a: legal basis for bias testing with special categories of personal data

    Editorially reviewed | fundamental-rights, high-risk-requirements

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

  75. ControlUpcomingv1.0.04 relations

    Review gate on a design change

    praxikon:eu:ai-act:control:design-change-review-gate

    The control that ensures no change to a legacy high-risk system reaches production without a recorded judgement on whether it is significant, with an identifiable assessor and a demonstrable link to the release.

    Hangs off: Article 111(2): legacy high-risk systems and the 2 August 2030 date

    Editorially reviewed | high-risk, timeline

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

  77. ControlEditorialv1.0.04 relations

    Protection of the person reporting

    praxikon:eu:ai-act:control:reporting-person-protection

    The control that ensures a report does not reach a line manager in identifiable form and that a person reporting who meets the conditions of Directive (EU) 2019/1937 is not treated differently afterwards. Article 19 of that Directive prohibits retaliation in any form, Article 21 sets out the protection and places the burden of proof on the organisation once the person reporting makes the detriment plausible. That is enforced not through the AI Regulation but through national whistleblower law. Without this control the channel exists but goes unused, and the first person who noticed something never reaches you.

    Hangs off: Article 87: reporting of infringements and protection of reporting persons

    Editorially reviewed | control, fundamental-rights

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

  79. DefinitionUpcomingv1.0.03 relations

    Annex III, point 1: biometrics

    praxikon:eu:ai-act:definition:annex-iii-area-1-biometrics

    Annex III, point 1, as that point stands in the Regulation, with its lettered subpoints and the exceptions named in them.

    Hangs off: Annex III: the eight areas separately

    Placed against the official source | high-risk

  80. DefinitionUpcomingv1.0.03 relations

    Annex III, point 2: critical infrastructure

    praxikon:eu:ai-act:definition:annex-iii-area-2-critical-infrastructure

    Annex III, point 2, as that point stands in the Regulation, with its lettered subpoints and the exceptions named in them.

    Hangs off: Annex III: the eight areas separately

    Placed against the official source | high-risk

  81. DefinitionUpcomingv1.0.03 relations

    Annex III, point 3: education and vocational training

    praxikon:eu:ai-act:definition:annex-iii-area-3-education-and-vocational-training

    Annex III, point 3, as that point stands in the Regulation, with its lettered subpoints and the exceptions named in them.

    Hangs off: Annex III: the eight areas separately

    Placed against the official source | high-risk

  82. DefinitionUpcomingv1.0.03 relations

    Annex III, point 4: employment and workers management

    praxikon:eu:ai-act:definition:annex-iii-area-4-employment-and-workers-management

    Annex III, point 4, as that point stands in the Regulation, with its lettered subpoints and the exceptions named in them.

    Hangs off: Annex III: the eight areas separately

    Placed against the official source | high-risk

  83. DefinitionUpcomingv1.0.03 relations

    Annex III, point 5: essential private and public services

    praxikon:eu:ai-act:definition:annex-iii-area-5-essential-private-and-public-services

    Annex III, point 5, as that point stands in the Regulation, with its lettered subpoints and the exceptions named in them.

    Hangs off: Annex III: the eight areas separately

    Placed against the official source | high-risk

  84. DefinitionUpcomingv1.0.03 relations

    Annex III, point 6: law enforcement

    praxikon:eu:ai-act:definition:annex-iii-area-6-law-enforcement

    Annex III, point 6, as that point stands in the Regulation, with its lettered subpoints and the exceptions named in them.

    Hangs off: Annex III: the eight areas separately

    Placed against the official source | high-risk

  85. DefinitionUpcomingv1.0.03 relations

    Annex III, point 7: migration, asylum and border control

    praxikon:eu:ai-act:definition:annex-iii-area-7-migration-asylum-and-border-control

    Annex III, point 7, as that point stands in the Regulation, with its lettered subpoints and the exceptions named in them.

    Hangs off: Annex III: the eight areas separately

    Placed against the official source | high-risk

  86. DefinitionUpcomingv1.0.03 relations

    Annex III, point 8: administration of justice and democratic processes

    praxikon:eu:ai-act:definition:annex-iii-area-8-justice-and-democratic-processes

    Annex III, point 8, as that point stands in the Regulation, with its lettered subpoints and the exceptions named in them.

    Hangs off: Annex III: the eight areas separately

    Placed against the official source | high-risk

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

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

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

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

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

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

  93. DefinitionIn forcev1.0.12 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  112. DefinitionIn forcev1.0.12 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

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

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

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

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

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

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

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

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

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

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

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

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

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

  126. DefinitionIn forcev1.0.12 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

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

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

  129. EvidenceUpcomingv1.0.04 relations

    Record of the mapping to a point of Annex III

    praxikon:eu:ai-act:evidence:annex-iii-area-mapping-record

    Per system: the intended purpose in your own words, the chosen point and lettered subpoint, the reasoning, the outcome of the Article 6(3) assessment with the condition it rests on, whether the system performs profiling, and for a reasoned no also the documentation and registration required by Article 6(4) and Article 49(2). Plus who assessed it and when. This is the document with which you later explain why the system was out of scope.

    Hangs off: Annex III: the eight areas separately

    Editorially reviewed | high-risk

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

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

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

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

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

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

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

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

  138. EvidenceEditorialv1.0.05 relations

    File accompanying a request to derogate from the conformity assessment

    praxikon:eu:ai-act:evidence:article-46-derogation-request-file

    Per request: which system and which version, which exceptional reason was invoked and on which facts, to which market surveillance authority and on what date the request was made, what the status of the conformity assessment was, which end date was agreed, when the notification of paragraph 3 was made, and what the outcome was.

    Hangs off: Article 46: derogation from conformity assessment procedure

    Editorially reviewed | conformity, enforcement, evidence

  139. EvidenceApplicablev1.0.07 relations

    Article 49 registration dossier

    praxikon:eu:ai-act:evidence:article-49-registration-dossier

    Per system: which Article 49 route was followed, the registration number, the date of registration, the name of the person who submitted it, the system version the entry relates to, and, for the secure section, a statement of which limited fields from Annex VIII and Annex IX were completed.

    Hangs off: Article 49: registration in the EU database before the system reaches the market

    Editorially reviewed | conformity, evidence, high-risk

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

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

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

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

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

  145. EvidenceApplicablev1.0.04 relations

    Information pack for subjects of testing in real world conditions

    praxikon:eu:ai-act:evidence:article-61-subject-information-pack

    The document that precedes consent: per test the five points of Article 61(1) written out, with the Union-wide unique single identification number, the contact details from whom further information can be obtained, and the mechanism for requesting the reversal or the disregarding of an output. This is a different item from the dated consent record itself, which sits in article-61-informed-consent-record.

    Hangs off: Article 61: informed consent of test subjects for testing in real world conditions

    Editorially reviewed | evidence, fundamental-rights, innovation

  146. EvidenceEditorialv1.0.04 relations

    File on SME status and facilities used

    praxikon:eu:ai-act:evidence:article-62-sme-status-record

    The substantiation of your status as an SME or start-up with the date, the evidence of a registered office or branch in the Union, and per facility what was applied for, with which body, on what date and with what outcome, including the answer to how the fee reduction was applied.

    Hangs off: Article 62: measures for providers and deployers that are SMEs or start-ups

    Editorially reviewed | evidence, governance, innovation

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

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

  149. EvidenceEditorialv1.0.05 relations

    Register of submissions to authorities

    praxikon:eu:ai-act:evidence:article-78-submission-register

    Per submission: which system, which document, which version, to which recipient, on what date, which part was marked confidential, and which purpose the recipient stated.

    Hangs off: Article 78: confidentiality of what you submit to an authority

    Editorially reviewed | enforcement, evidence, governance

  150. EvidenceEditorialv1.0.04 relations

    Register of voluntary commitments alongside the obligations

    praxikon:eu:ai-act:evidence:article-95-voluntary-commitment-register

    Per system and per commitment: which requirements you apply voluntarily, under which paragraph of Article 95, with which objectives and key performance indicators, who owns it, when it is measured, and which obligation under the Regulation continues to apply in full alongside it.

    Hangs off: Article 95: codes of conduct for voluntary application of specific requirements

    Editorially reviewed | evidence, governance, innovation

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.