Product
Seven chapters, from inventory to a public verifier.
The same path the regulation takes: list what you run, classify it, read the obligations by date, document and prove them, report when you must, and keep the two duties everyone owes. The seventh chapter is ours alone: Art. 50 for AI voice.
Every AI system in one register, with an owner.
Bought, built or embedded: each entry carries its intended purpose, its role under the Act, the vendor, the people it affects and the person responsible. Drift is visible: a changed purpose re-opens the classification.
Art. 3(1) definition · Art. 3(12) intended purpose · Art. 25 change of role
AI inventory
- CV screening (vendor SaaS)High-risk
- Customer chatbotTransparency
- Demand forecastingMinimal
Nine questions, in the order the regulation asks them.
Role, EU scope, prohibited practices, general-purpose models, Annex I, Annex III, the Art. 6(3) exemptions with the profiling override, transparency flags and the SME flag. The assistant proposes with verbatim quotes; a named person decides and the decision is logged.
Art. 2 · Art. 5 · Art. 6 · Annex I and III · Art. 50 · Art. 62
Classification wizard
- 1Role: deployer or provider?
- 2EU scope: placed on the market or used in the Union?
- 3Art. 5: any prohibited practice?
- 4Annex III: listed area?
- 5Art. 50: interacts with people or generates content?
Role and risk class are set by a person, never by the assistant.
A register of duties, grouped by when they bite.
Each obligation shows the article text in your language, the date it applies from under Art. 113 and 111, the evidence that satisfies it and the owner. Three waves on every system: in force, due next, due later.
Art. 113 application dates · Art. 111 transitional rules · corpus version shown on every page
Obligations by wave
In force
- Art. 4 AI literacy
- Art. 50(1) chatbot disclosure
Due next
- Art. 26 deployer duties
- Art. 27 fundamental rights impact assessment
Due later
- Annex I product obligations
Templates that know which section is still empty.
Deployer and provider template sets: literacy record, Art. 50 notice, deployment record, FRIA, Annex IV technical file, QMS outline. Sections carry coverage badges, uploads get a SHA-256 hash in the evidence ledger, and exports are stamped with the corpus version.
Art. 11 and Annex IV · Art. 18 record keeping · Art. 26(6) logs · Art. 27
Document coverage
- AI literacy recordcomplete
- Art. 50 notice (EN/DE)complete
- Fundamental rights impact assessment3 of 7 sections
- Technical documentation, Annex IVnot started
Evidence ledger · 12 files · SHA-256
One number per system, and the filing when the clock starts.
Readiness is the share of applicable checks with evidence behind them, by wave and by system. Filings are type-driven forms: EU database registration, the Art. 73 incident report with its 15, 10 and 2-day clocks, frozen on submission and exportable.
Art. 49 registration · Art. 71 EU database · Art. 73 serious incidents
Readiness by wave
- In force90%
- Due next55%
- Due later20%
Art. 73 incident report
Clock: 15 days · started 3 days ago
frozen on submission
The two duties every organisation already owes.
Art. 4 asks for measures: a roster, programmes, dated attestations and a CSV import for the people team. Art. 50 asks for disclosure and marking: a notice snippet in English and German, an embed, a marking policy and a public verifier link per disclosure.
Art. 4 since 2 February 2025 · Art. 50 since 2 August 2026 · Germany: KI-MIG in force 29 July 2026, Bundesnetzagentur as market surveillance authority
AI literacy roster
- People team · 6 of 6 attested
- Sales · 9 of 14 attested
- Engineering · 4 of 11 attested
Art. 50 notice
You are talking to an AI system. A person can take over on request.
Mark, detect, consent, verify.
Generated speech is signed with C2PA metadata and carries an imperceptible watermark; the consent of the voice owner is recorded with scope and expiry; a free hosted verifier reads both layers and the disclosure record. The Code of Practice of 10 June 2026 asks for exactly these two layers and free detection; interoperable detection is due 2 February 2027.
Art. 50(2) and (4) · Art. 111(4) marking deadline 2 December 2026 for existing generative systems · Commission guidelines C(2026) 5054 of 20 July 2026
Art. 50 audio pipeline
- 01Mark: C2PA manifest + imperceptible watermark
- 02Detect: both layers read back, logged per file
- 03Consent: voice owner, scope, expiry, countersigned
- 04Verify: public page per disclosure, free
Audible disclaimer for audio-only deep fakes per the Code of Practice
How we run it
Built to be shown to an auditor.
- Hosted in the EU, with a data processing agreement
- Official EN and DE text of the Act, with the corpus version shown
- No training on your documents
- Self-hosted fonts and cookieless analytics, so no cookie banner
- SSO, SCIM and two-factor authentication
- Export everything, any time
- We apply Art. 50 to ourselves: AI-drafted text is always marked
Start with one AI system.
Run the free check, keep the result as your first inventory entry, and invite your team when you are ready.