ARTICLE 50 TRANSPARENCY WORKSPACE

Map the actor, content, obligation, evidence, and disclosure route.

This front-end workspace helps separate applicability from implementation and evidence. It does not make a legal determination. It creates a bounded assessment record showing which Article 50 pathways were considered, what evidence was declared, what remains missing, and where independent review is required.

Demonstration assessment only.

No account persistence, file upload, regulator submission, legal interpretation, conformity assessment, or compliance certification is connected to this page.

ASSESSMENT BUILDER

Declare the context before selecting the obligation.

STEP 01 · ACTOR ROLE

What role is being assessed?

STEP 02 · CONTENT OR INTERACTION TYPE

What does the system generate, manipulate, or present?

STEP 03 · OBLIGATION PATHWAY

Select pathways requiring assessment

Only pathways matching the declared role and content are displayed.

Article 50(1)TA-14-A50-01

Direct interaction with an AI system

Natural persons interact directly with an AI system unless the interaction is obvious from the circumstances and context of use.

Provider · Provider and DeployerInteractive AI
Article 50(3)TA-14-A50-03

Emotion recognition and biometric categorisation notice

Natural persons are exposed to an emotion-recognition or biometric-categorisation system and an applicable exception has not been established.

Provider · Deployer · Provider and DeployerInteractive AI · Image · Video
STEP 04 · EVIDENCE DECLARATION

Which evidence items are presently available?

Selecting an item only records a declaration in this browser state. It does not validate, upload, inspect, or authenticate the evidence.

SELECTED PATHWAY DETAILS

What must be tested, and what must not be overstated?

Article 50(1)TA-14-A50-01

Direct interaction with an AI system

Implementation questions
  • Does the user interact directly with the AI system?
  • Would a reasonable person understand from context that the system is AI?
  • When is the disclosure first presented?
  • Can the disclosure be distinguished from ordinary interface content?
  • Does the disclosure remain present after material interface changes?
Claims this record cannot support by itself
  • A chatbot label alone does not prove sufficient disclosure.
  • A policy document does not prove the disclosure appeared to users.
  • A design mock-up does not prove production deployment.
GOVERNED OUTPUT PACKAGE

A complete route should produce separate records.

Applicability Record

Actor, system, content type, deployment context, obligation considered, exception considered, and unresolved interpretation.

Evidence Map

Each claimed measure bound to evidence identity, owner, version, date, location, and validation state.

Implementation Record

The actual marking, notice, disclosure, interface, workflow, or publication mechanism used.

Testing Record

Detectability, persistence, placement, timing, robustness, failure states, and technical limitations.

Independent Review Record

Reviewer, scope, evidence inspected, objections, corrections, findings, and limitations.

Change and Outcome Record

What changed, what was approved, held, denied, escalated, superseded, or left unresolved.

SEPARATE THE RECORD FROM THE DETERMINATION

An Article 50 checklist is not an admissible transparency record.

The assessment must preserve who made the claim, what role they occupied, what content was involved, which obligation was considered, what evidence existed, what remained missing, who reviewed the route, and what conclusion the evidence could actually support.

TA-14 Exchange Activity

Public activity recorded across the Exchange

Visitors

Page Views