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

43 objects in this selection.

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

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

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

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

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

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

  7. ChangeUpcomingv1.0.02 relations

    Grace period for machine-readable marking ends

    praxikon:eu:ai-act:change:2026-12-02-article-50-marking-grace-ends

    Systems placed on the market before 2 August 2026 must comply with Article 50(2) by 2 December 2026.

    Hangs off: Article 50: transparency

    Placed against the official source | timeline, transparency

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  25. ExampleGuidancev1.0.02 relations

    A webshop helpdesk chatbot must announce itself

    praxikon:eu:ai-act:example:example-helpdesk-chatbot-meldt-zichzelf

    A webshop runs an AI chatbot for questions about orders, delivery and returns. The bot writes fluent prose, carries a staff profile picture, and nowhere does it say that no human is reading along.

    Hangs off: Article 50: transparency

    Placed against the official source | examples

  26. ExampleGuidancev1.0.02 relations

    Internal AI assistant for trained staff needs no notice

    praxikon:eu:ai-act:example:example-interne-ai-assistent-evidente-interactie

    An organisation makes an internal AI assistant available for HR, procurement, IT and compliance questions. It sits behind the company login only, and staff have been trained in using AI.

    Hangs off: Article 50: transparency

    Placed against the official source | examples

  27. ExampleGuidancev1.0.02 relations

    In-car navigation: lighter marking is enough

    praxikon:eu:ai-act:example:example-navigatiesysteem-metadata-markering

    A car manufacturer builds a generative AI system into the navigation unit that composes spoken and written route instructions. The output stays inside the vehicle and technical measures prevent it from being exported or shared.

    Hangs off: Article 50: transparency

    Placed against the official source | examples

  28. ExampleGuidancev1.0.02 relations

    Satirical deep fake of a politician: lighter, not exempt

    praxikon:eu:ai-act:example:example-satirische-deepfake-van-politicus

    A satirical outlet publishes an AI-manipulated image of an existing politician, placed in a scene that humorously criticises a policy decision. Style and context make it immediately clear that this is satire.

    Hangs off: Article 50: transparency

    Placed against the official source | examples

  29. ExampleGuidancev1.0.02 relations

    Spell checking needs no marking, an AI summary does

    praxikon:eu:ai-act:example:example-spellingcorrectie-versus-ai-samenvatting

    A publisher uses the same AI tool for two things: correcting spelling and cleaning up formatting in submitted pieces, and producing summaries and rewrites of those same pieces.

    Hangs off: Article 50: transparency

    Placed against the official source | examples

  30. ExampleGuidancev1.0.02 relations

    A synthetic avatar of your own CEO is a deep fake

    praxikon:eu:ai-act:example:example-synthetische-avatar-van-de-ceo

    A company has a realistic synthetic avatar of its own CEO deliver a new year message thanking employees for last year's results. The video goes to the intranet and to the company's social media channels.

    Hangs off: Article 50: transparency

    Placed against the official source | examples

  31. GuidanceGuidancev1.0.03 relations

    AI agents must disclose both their AI nature and on whose behalf they act

    praxikon:eu:ai-act:guidance:guidance-article-50-ai-agent-self-disclosure

    An AI agent that makes bookings, handles correspondence or concludes contracts must identify itself as AI and state on whose behalf it is acting, including towards the person instructing it.

    Hangs off: Article 50: transparency

    Placed against the official source | guidance

  32. GuidanceGuidancev1.0.02 relations

    Artistic or satirical work is not exempt but attenuated, and the informative character always prevails

    praxikon:eu:ai-act:guidance:guidance-article-50-artistic-attenuated-disclosure

    For deep fakes in evidently artistic, creative, satirical or fictional work, the disclosure must not hamper the work, but it remains mandatory. Where the content mixes in an informative or commercial character, the standard label applies.

    Hangs off: Article 50: transparency

    Placed against the official source | guidance

  33. GuidanceGuidancev1.0.03 relations

    Signing the code of practice is voluntary, but not signing means proving it yourself

    praxikon:eu:ai-act:guidance:guidance-article-50-code-of-practice-effect

    Signing the code of practice on transparency of AI-generated content is voluntary and not signing is not in itself non-compliance. Those who do not sign must demonstrate compliance by other means, including a gap analysis against the code.

    Hangs off: Article 50: transparency

    Placed against the official source | guidance

  34. GuidanceGuidancev1.0.02 relations

    The deployer cannot rely on the provider's machine-readable marking

    praxikon:eu:ai-act:guidance:guidance-article-50-deployer-perceivable-labelling

    Whoever publishes a deepfake must apply a label perceivable by humans. The watermark or metadata supplied by the provider does not discharge that duty.

    Hangs off: Article 50: transparency

    Placed against the official source | guidance

  35. GuidanceGuidancev1.0.03 relations

    Disclosure at the latest at first interaction, and again for every new person

    praxikon:eu:ai-act:guidance:guidance-article-50-disclosure-timing

    The notice that a person is dealing with an AI system must be given at the latest at the time of the first interaction. That moment applies per natural person, not once per system.

    Hangs off: Article 50: transparency

    Placed against the official source | guidance

  36. GuidanceGuidancev1.0.02 relations

    The editorial exception: substantive review plus an identifiable responsible person

    praxikon:eu:ai-act:guidance:guidance-article-50-editorial-control-exception

    No label is needed where the AI text has been substantively reviewed by a human and someone holds editorial responsibility. A spellcheck or a written editorial policy is not enough, and any AI intervention after sign-off voids the exception.

    Hangs off: Article 50: transparency

    Placed against the official source | guidance

  37. GuidanceGuidancev1.0.03 relations

    What does not suffice on its own as an AI disclosure

    praxikon:eu:ai-act:guidance:guidance-article-50-insufficient-disclosure-methods

    A line in the terms and conditions, a hidden metadata mark or a vague word like 'assistant' will not do. The guidelines name five methods that are insufficient when used alone.

    Hangs off: Article 50: transparency

    Placed against the official source | guidance

  38. GuidanceGuidancev1.0.03 relations

    Existing systems and legacy content: what does and does not apply retroactively

    praxikon:eu:ai-act:guidance:guidance-article-50-legacy-content-and-transition

    Only the machine-readable marking under Article 50(2) has a transitional period for systems already on the market. Legacy content need not be labelled retroactively, but legacy text you publish now must be.

    Hangs off: Article 50: transparency

    Placed against the official source | guidance

  39. GuidanceGuidancev1.0.02 relations

    When is AI obvious? The exception applies only where almost no doubt remains

    praxikon:eu:ai-act:guidance:guidance-article-50-obvious-ai-exception

    The exception for obvious AI interaction must be interpreted restrictively. It applies only where almost no doubt remains for an average member of the intended and reasonably foreseeable audience.

    Hangs off: Article 50: transparency

    Placed against the official source | guidance

  40. GuidanceGuidancev1.0.02 relations

    Standard editing versus semantic change under the marking obligation

    praxikon:eu:ai-act:guidance:guidance-article-50-standard-editing-exception

    Spellchecking, formatting and minor image corrections fall outside the marking obligation. An AI summary, rewrite or face replacement falls inside it.

    Hangs off: Article 50: transparency

    Placed against the official source | guidance

  41. GuidanceGuidancev1.0.02 relations

    Which AI text needs a label: published, informing the public, on a matter of public interest

    praxikon:eu:ai-act:guidance:guidance-article-50-text-public-interest-scope

    The labelling duty for AI text applies only where three elements coincide: the text is published, is intended to inform the public, and concerns a matter of public interest.

    Hangs off: Article 50: transparency

    Placed against the official source | guidance

  42. ObligationApplicablev1.0.048 relations

    Article 50: transparency

    praxikon:eu:ai-act:obligation:article-50-transparency

    Specific disclosure, marking and labelling duties for certain AI systems and synthetic content.

    Placed against the official source | transparency

  43. Templatev1.0.04 relations

    Article 50 checklist

    praxikon:eu:ai-act:template:article-50-checklist

    Public decision route for the distinct transparency obligations.

    Hangs off: Article 50: transparency

    Editorially reviewed | template, transparency

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.