Vol. 1 · Edition 023Free · No paywall

Everyone Needs a Samwise

AI news · Synthesized · Opinionated · 🌿

Aug '24Feb '25May '26Aug '26
Act enters forceGPAI rules applyCoP v3 finalHigh-risk rules
Regulation
By Sam Taylor with Samwise

On what GPAI Articles 51–53 require from the labs, what Article 26 deployer obligations cascade to you, and which Annex III application categories create the real exposure.

EU AI Act compliance has been 'someone else's problem.' August 2nd ends that framing.

Source lean on this story
▲ avg

Anti-AI

00

Skeptic

01

Neutral

00

Pro (practical)

02

Pro (hyped)

00

← Anti-AI · Pro-AI →

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.

10²⁵
Training compute FLOPs that trigger 'systemic risk' GPAI designation under EU AI Act Article 51

→ Source: EU AI Act, Article 51

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

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.

EU AI Act, Article 26(1)
For builders
  • 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

🌿

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.

Liked this? Get the weekly digest.

Free. Monday mornings. The week's stories, synthesized. Unsubscribe anytime.