EU AI Act Article 50 Transparency Kit (engineering checklist)

An informational engineering aid for the AI Act's Article 50 transparency obligations, which apply from 2 August 2026 per the European Commission. Includes: a plain-language checklist mapped to 50(1)-(5), with official EU sources only; questions to bring to counsel; disclosure and label templates for chat, voice, agent email, synthetic media and AI-generated text; a systems inventory and an evidence register; and transparency_check.py, which flags missing assessments, missing evidence and outputs without a disclosure phrase. Not legal advice and not a compliance determination; consult counsel.

Doc / JSON / CSV / Python script (ZIP + PDF)An informational engineering aid for the AI Act's Article 50 transparency obligations, which apply from 2 August 2026 per the European Commission. Includes: a plain-language checklist mapped to 50(1)-(5), with official EU sources only; questions to bring to counsel; disclosure and label templates for chat, voice, agent email, synthetic media and AI-generated text; a systems inventory and an evidence register; and transparency_check.py, which flags missing assessments, missing evidence and outputs without a disclosure phrase. Not legal advice and not a compliance determination; consult counsel.

The Agent Cyber Defense Dashboard, which pairs with the EU AI Act Article 50 Transparency Kit (engineering checklist) (sample walkthrough data)
Sample walkthrough data · Agent Cyber Defense Dashboard

What's inside

Verify it works

  1. python3 transparency_check.py --selftest prints selftest ok.
  2. python3 transparency_check.py systems_inventory.json evidence_register.csv --today 2026-10-22 lists gaps for the example systems: missing 50(4) evidence for marketing-images, open evidence rows and 50(5) reminders. It exits 1 while gaps remain.
  3. Replace the examples with your own AI features. Re-run until only items you've discussed with counsel remain.
  4. python3 transparency_check.py --label-scan page.html email.txt checks that your rendered outputs contain a disclosure phrase. Edit PHRASES for your own wording and languages.
  5. Read the official sources linked in 01_Article_50_Engineering_Checklist.md. This kit is not legal advice and doesn't establish compliance. Python 3.9+, no installs.

Preview

First part of the main document, shown as-is:

EU AI Act Article 50: an engineering checklist for transparency

Not legal advice. This is an informational engineering aid. It summarizes official EU sources in plain words so that product and engineering teams can prepare questions and evidence for their legal counsel. It does not tell you whether the AI Act applies to you, which role you hold, or whether your measures comply. Using it does not make you compliant. Consult qualified counsel, and read the official texts below; they take precedence over anything here.

Official sources (read these, they are authoritative)

Key dates, as stated by the Commission (checked Oct 22, 2026)

Step 1. Inventory and role questions for counsel

For each AI feature, record the following in systems_inventory.json: - What it does, who sees its output, and whether people in the EU interact with it or see its output. - Whether your organization is the provider (develops the system or has it developed, and places it on the market under its own name) or the deployer (uses it under its authority) for this feature. This is a legal determination. Write down your working assumption and the question for counsel. - Which Article 50 situations may be relevant (step 2). The Commission guidelines give in-scope and out-of-scope examples.

← All kits