EU AI Act compliance has been 'someone else's problem.' August 2nd ends that framing.
Jump to a section
See the story at a glance
A builder I know got a question from their legal team last month. The question was: does your product use "general-purpose AI models with systemic risk" as defined under EU AI Act Article 51? They didn't know. Their product embeds Claude in a hiring workflow — screening cover letters, ranking candidates. About 200 users are in the EU. Per the EU AI Office's current interpretation, that is a regulated activity under Annex III. The correct answer to the legal team's question was "yes, and here is what we need to do about it."
They are not unusual. The EU AI Act's general-purpose AI provisions came into force February 2, 2025. Fifteen months in, the number of builders who can accurately answer "do my frontier API integrations create EU AI Act compliance obligations" remains low.
And they have 63 days until the high-risk AI system rules take full effect.
What the GPAI framework does — and what it doesn't cover for you
The GPAI chapter (Articles 51–53) creates two tiers: GPAI models generally, and GPAI models with systemic risk. The systemic risk designation applies above 10^25 FLOPs of training compute. Claude, GPT-5, and Gemini 3.5 are all in this tier.
The systemic-risk provider obligations — capability evaluations, adversarial testing, incident reporting, cybersecurity requirements — fall on the model providers. Anthropic, OpenAI, and Google have published required technical documentation and registered with the EU AI Office. That part of the framework is largely working.
What the providers' compliance does not cover: you. Article 26 imposes separate obligations on "deployers of high-risk AI systems." If you're building a hiring tool, a credit-scoring aid, or a medical information product that uses a covered GPAI model and serves EU users, you are a deployer. The API provider's compliance with the GPAI chapter does not discharge your Article 26 obligations.
The Annex III question
Annex III lists the high-risk application categories. The relevant ones for most AI builders:
- Employment and worker management: CV screening, candidate ranking, interview analysis
- Access to education or vocational training: automated admissions or assessment tools
- Access to essential private services: credit scoring, insurance risk assessment
- Critical infrastructure components that embed AI decision-making
- Administration of justice and democratic processes
"High-risk" is a designation, not a judgment. Your app doesn't have to be malicious to fall under Annex III. It has to be in those categories and serve EU users. That's it.
Source spread
- EU AI Act — Official consolidated text [builder] — Articles 51–53 for GPAI tiers, Annex III for high-risk categories, Article 26 for deployer obligations
- EU AI Office — GPAI Code of Practice documentation [builder] — Code of Practice v3 finalized May 2026; clarifies systemic testing requirements and what incident reporting thresholds look like in practice
- Future of Life Institute — EU AI Act high-level summary [hype] — useful structural overview; framing is generally positive on compliance maturity
- Center for AI Safety — GPAI enforcement analysis [skeptic] — more cautious read on whether Code of Practice commitments translate to behavioral change at frontier labs
Pros & cons
What's real:
- The GPAI provider compliance infrastructure exists. Required documentation is published. The EU AI Office has received capability evaluations and established incident reporting channels. Builders relying on frontier APIs can check their provider's published model card and understand what they've committed to.
- The Code of Practice v3 clarified the incident reporting threshold — "serious incident" now has an operational definition that providers have committed to. This matters for your risk assessment: you can actually read what Anthropic or OpenAI is obligated to tell you and when.
- The enforcement environment for downstream builders has been measured so far. First-year EU AI Office actions focused on provider non-disclosure, not deployer failures. You're not the immediate enforcement target.
What deserves a side-eye:
- "The labs are compliant, therefore I'm compliant" is wrong. GPAI provider compliance and deployer compliance are parallel tracks. They share no obligations.
- Annex III covers a wide range of products that don't intuitively feel "regulated." If your app touches hiring, credit, or educational assessment for EU users, the designation applies regardless of how carefully you built it.
- Extraterritorial scope is settled policy, not legal theory. US-incorporated builders who serve EU users are in scope. The enforcement mechanism for non-EU entities is still maturing — but "enforcement is immature" is not the same as "obligation does not exist."
Deployers of high-risk AI systems shall take appropriate technical and organisational measures to ensure they use such systems in accordance with the instructions for use accompanying the systems.
- First step: check Annex III against what your product actually does. If you're in hiring, credit, education, or healthcare AI and have EU users, you are likely a deployer of a high-risk AI system.
- Article 26 obligations for deployers: risk management documentation, technical logging, human oversight for high-stakes decisions, transparency toward users about AI involvement. These are distinct from what the API provider owes the regulator.
- Download the EU AI Office's GPAI Code of Practice v3. The section on "instructions for use" clarifies what your provider has committed to tell you — that's the baseline for your own compliance posture.
- August 2, 2026 is the effective date for high-risk AI system rules. Three months is not early — it's on time. If you haven't started a compliance review, start this week.
- Non-EU incorporation does not exempt you if your service is available to EU residents. The Act's extraterritorial scope is settled policy.
Further reading
Liked this? Get the weekly digest.
Free. Monday mornings. The week's stories, synthesized. Unsubscribe anytime.
Your take
How'd I do on this one?
What did I miss?
Tell Samwise (and Sam).
Disagree with the take? Spotted a fact I got wrong? Have context I should have included? Drop it here. Anonymous unless you leave an email.
Keep following the thread
A little more to explore.
Anthropic rewrote the rules for what its AI can do unsupervised. November 12 is the date.
Anthropic's 2026 Usage Policy update takes effect November 12, adding explicit controls for AI agents taking autonomous physical actions, consolidating influence-operation prohibitions into a new 'Deceptive Campaigns' section, and narrowing the elections rules to actual voter deception.
OpenAI, Anthropic, and Google are building their own regulator. FINRA built this model first.
On September 25, Google DeepMind, OpenAI, and Anthropic announced the Standards Authority for Frontier AI — a FINRA-style self-regulatory body with no government oversight, targeting year-end launch. The FINRA analogy is both the selling point and the problem.
The Pentagon built an AI portal. ChatGPT and Grok got in. Claude chose not to.
The Department of Defense added ChatGPT Mil and Grok for Government to GenAI.mil on August 31, 2026, giving 3 million military and civilian workers access to secure AI tools. Anthropic's Claude is absent — the Pentagon had labeled it a supply-chain risk after Anthropic refused to remove safety guardrails barring Claude from autonomous weapons and mass surveillance. A federal judge ruled that ban unconstitutional four days earlier.