AI Compliance Package — EU Article 50 plus US module
Article 50 has been in force since 2 August 2026.
Three weeks: the transparency and marking controls the regulation asks for, running in production, plus the optional US state module.
3 weeks · $15-25K · Signed off by DPO, General Counsel, or Head of Compliance
2 Aug 2026
Article 50 transparency obligations applicable
2 Dec 2026
End of the marking grace period for legacy systems
2 Dec 2027
Annex III high-risk obligations
Technical readiness, not legal advice. The controls, the mechanics, and the evidence get built and verified. Whether an obligation applies to you is counsel's call — the engagement runs alongside them, and introductions to specialist counsel are part of the package.
Who this is for
- You operate a system that interacts with people or generates synthetic content, and you sell into the EU.
- Counsel has told you what the obligation is and nobody has translated it into controls that run.
- You need the evidence to exist before a regulator, a customer, or an auditor asks for it.
And who it is not
- You need a legal opinion on whether an obligation applies. That sits with counsel, and the engagement is built to run alongside them — the technical work maps to their position, and introductions to specialist counsel are part of the package.
- You are a frontier developer above the compute thresholds. Those obligations are a different regime, with specialist advisors built for it.
What you get
- A classification pass: which of your systems fall under which obligation, and on what date.
- Transparency controls: disclosure at the interaction boundary, implemented in the product rather than the terms of service.
- Content marking and provenance mechanics for synthetic output, including the legacy-system path.
- Record-keeping and audit trails sized to what the obligation actually requires.
- A roadmap to the Annex III deadline for anything that will land in the high-risk category.
- Optional US module: Texas TRAIGA disclosure and NIST AI RMF alignment, Colorado preparation, California marking obligations.
How it runs
Week 1
Classification
Which systems, which obligations, which dates. Done with your counsel, not instead of them, so the technical work maps to a legal position someone will stand behind.
Week 2
Controls
Disclosure, marking mechanics, and record-keeping built into the product path and verified against real output.
Week 3
Evidence and roadmap
The evidence pack assembled, and the route to the December 2027 obligations laid out for whatever will land in Annex III.
This has shipped
Read the code first
What it costs
$15-25K
The EU module is the base. The US state module (Texas, Colorado, California) is scoped separately depending on where you operate.
Every engagement can start as a $2,500 paid pilot, credited in full against the full scope if you go ahead.
Every engagement and what it costsBefore you talk to anyone
EU AI Act Article 50 Self-Assessment
Which transparency obligations apply to your system, who owes them, and from which date. Free, runs in your browser, and nothing you type leaves it.
Open the eu ai act article 50 self-assessmentQuestions people actually ask
Are you giving legal advice?
No — technical readiness only: the controls, the mechanics, and the evidence. The interpretation sits with counsel, and the work is built to slot straight into their legal position.
The high-risk deadline moved. Does that mean we can wait?
The Annex III date moved to December 2027. Article 50 transparency did not — it has been applicable since 2 August 2026, and the marking grace period for legacy systems ends 2 December 2026. The deferred deadline is the one people talk about; the live one is the one that applies today.
We are a US company. Does any of this matter?
If you sell into the EU, yes. Separately, the US state layer is live in its own right — Texas has been in force since January 2026, California's marking obligation landed in August 2026, and Colorado arrives January 2027. The deadline tracker on this site lists them with sources.
How do we verify the dates you quote?
Every date on the tracker links to primary source — EUR-Lex, the state legislature, or the statute itself — and the tracker is re-checked monthly. Verify anything you plan around; the sources are one click away.
Fifteen minutes is enough to work out whether this is the right engagement, or whether it is one of the others, or none of them.
Book a 15-min callScoping by email works too — send what you're building and the read-back comes with a recommendation on where to start — even when the right start is smaller than you expected.
The technical control checklist for each obligation the assessment flags, and the evidence a reviewer will ask you to produce.