The lever points the other way — the AI Act channel only downstream providers can use

The AI Office's complaints channel for downstream providers, published on 31 July 2026 and operable since enforcement began on 2 August, is the one AI Act route that points at a team's model supplier rather than at the team. It rests on Article 89(2), which gives downstream providers a right — not a form — to lodge a duly reasoned complaint naming three things, and it covers Articles 53 to 55. The clause that matters to an engineer is 53(1)(b): the provider's duty to hand over documentation sufficient to understand the model's capabilities and limitations, with Annex XII as the floor — context window and maximum input and output size, architecture and parameter count, the technical means to integrate, and the type, provenance and curation of training, testing and validation data. Two traps: the general complaints tool's own scope note excludes Articles 53 to 55 and Article 89(2) matters, and the channel is not anonymous. One gap: Article 53(2) lifts the duty entirely for free and open-source models with public parameters and architecture, unless the model carries systemic risk.

Post

For two weeks the AI Act coverage has been about what model providers owe regulators.

One channel opened on 2 August points the other way — at your supplier, and only you can use it.

The AI Office runs three reporting routes now, and they are not interchangeable. The one that matters if you ship agents on someone else's model is the complaints channel for downstream providers. It rests on Article 89(2): "Downstream providers shall have the right to lodge a complaint alleging an infringement of this Regulation."

Not a form. A right.

It covers Articles 53 to 55. The one about you is 53(1)(b): the provider's duty to give you documentation sufficient to understand the model's capabilities and limitations and meet your own obligations. Annex XII sets the floor.

Read what that floor includes. Context window and maximum input and output size. Architecture and number of parameters. The technical means required to integrate the model. The type and provenance of training, testing and validation data.

Now look at the model card you were actually given.

Two things engineers get wrong. The general AI Act complaints tool cannot take this — its own scope note excludes Articles 53 to 55 and Article 89(2) matters. And it is not anonymous: you give identification and contact details, and you get a reference number back. Anonymity is the whistleblower tool, and that one is for insiders, not customers.

Then the gap. Article 53(2) lifts 53(1)(a) and (b) for models released under a free and open-source licence with public parameters and architecture, unless the model has systemic risk. Build on open weights and there is no duty owed to you.

What I'd do Monday:

  1. Diff Annex XII against the pack your provider actually gave you. That list is your gap register.
  2. Ask in writing for what is missing. A complaint needs a record and a date.
  3. Mark which models are open-weight. There the annex is a negotiation, not a right.
  4. Name someone who owns supplier documentation. The right goes unused because nobody is assigned to it.

The Act spent two years being described as a cost on the people who build. This is the clause where it is leverage.

Which Annex XII item can you not answer for your production model this morning?

#AgenticAI #EUAIAct #AIEngineering #AIGovernance #Berlin

AI disclosure: the narration voice, the cover art and the brand ident animation in this video are AI-generated. The script, the claims and the source checks are mine.

First comment

Sources, primary first —

European Commission, published 31 July 2026 — the downstream-provider complaints channel itself: who qualifies, what a submission must contain, the reference number, and the mailbox https://digital-strategy.ec.europa.eu/en/miscellaneous/complaints-channel-downstream-providers-using-general-purpose-ai-models

The AI Act enforcement framework, last updated 7 August 2026 — the three channels side by side https://digital-strategy.ec.europa.eu/en/policies/enforcement-ai-act

The general AI Act complaints tool — read the scope note, which is where it says Articles 53 to 55 and Article 89(2) matters do not belong here https://digital-strategy.ec.europa.eu/en/policies/ai-act-complaints-tool

AI Act Article 89 — paragraph 2 is the right itself, and points (a) to (c) are the three things a complaint must name https://artificialintelligenceact.eu/article/89/

AI Act Annex XII — the floor of what a model provider owes a downstream provider https://artificialintelligenceact.eu/annex/12/

AI Act Article 53 — the duty at 53(1)(b), and the open-source lift at 53(2) https://artificialintelligenceact.eu/article/53/

Commission press release, 2 August 2026 — enforcement start https://ec.europa.eu/commission/presscorner/detail/en/ip_26_1714

One point cut for length: Article 89(2) gives you a right to complain, not a remedy. There is no stated deadline for the AI Office to act, no damages, and no order compelling the document. What it gives you is a file with a date on it — which, if your own regulator later asks why your Article 15 accuracy claim rests on numbers you could not obtain, is the difference between a gap and a documented one.

Claims

Sources

Corrections

No corrections issued for this edition.

AI disclosure

The video for this edition contains AI-generated media: the narration is a synthetic voice and the cover art is generated. The script, the claims and the source verification are human-authored and human-checked. Assets carry IPTC DigitalSourceType and C2PA Content Credentials.