FOXNUT

Definition

What does EU AI Act compliance ask of operators?

EU AI Act compliance turns on your role and your system's risk tier. High-risk dates moved in July 2026. This is description, not legal advice.

By the Foxnut team · Updated

What is EU AI Act compliance, and who does it reach?

EU AI Act compliance turns on two questions: which role a company plays under the Act (provider, deployer, importer, distributor), and which risk tier the system falls into. Regulation (EU) 2024/1689 is the EU AI Act, the European Union’s law governing AI systems.

We are Foxnut Studios, a senior-only practice in Bengaluru and Paris that builds AI systems and hands them over, so this law sits over half of our own footprint. There’s a link to talk to us at the end of this article. Let’s first get straight who the Act reaches and what applies when.

Its reach does not stop at Europe’s border. Under Article 2, the Act applies to providers placing AI systems on the EU market irrespective of where they are established, and to providers and deployers in third countries whenever the system’s output is used in the Union. A company entering the European market with AI inside its product, or running AI on work for European customers, can be in scope without ever opening an office there.

This page holds the Act the way an operator entering Europe needs to hold it: what already applies, what changed in July 2026, and which questions to take into the market.

Important note: this page describes and does not advise. What the law requires of a specific company is a question for licensed counsel in the target market, which is the boundary the AI consulting territory at Foxnut Studios keeps on every regulatory subject, in Europe and everywhere else we build.

Which EU AI Act compliance dates have already passed?

Most of the Act’s early dates have passed. The Act entered into force on 1 August 2024 and applies in phases, so an operator reading about it now is reading about a law already partly in application.

The bans on certain AI practices and the AI literacy obligation have applied since 2 February 2025. The obligations on providers of general-purpose AI models, and the Act’s governance machinery, have applied since 2 August 2025. The Act’s general application date, the default for everything not given its own date, including the transparency obligations described below, was 2 August 2026.

Every date, with the article it comes from and a source per row, sits in the dated milestone table for the Act. This page carries the structure, and that one carries the numbers.

What changed in the EU AI Act in July 2026?

The high-risk application dates moved, so the timeline most published guides still describe is no longer the timeline. On 8 July 2026 the EU adopted Regulation (EU) 2026/1744, the “Digital Omnibus on AI”, which entered into force on 27 July 2026.

Rules for systems in the Act’s listed high-risk areas (biometrics, critical infrastructure, education, employment, migration and border control among them) now apply from 2 December 2027, and rules for AI embedded in regulated products such as lifts or toys apply from 2 August 2028. The stated reason is the delayed availability of harmonised standards and national authorities.

For an operator the consequence is blunt. Any AI Act summary written before mid-2026 is out of date on exactly the dates that matter most, and is worth re-checking against the amending regulation before it informs a plan.

How does the Act sort AI systems into risk tiers?

The Act sorts systems by what they do, and the tier decides the obligation. It is not one set of rules but several. The table below lays out the tiers and where each one stands after the July 2026 amendment.

TierWhat it coversWhere it stands today
Prohibited practicesAI uses the EU has banned outrightIn application since 2 February 2025
High-risk, listed areasSystems used in areas listed by the Act: biometrics, critical infrastructure, education, employment, migration and othersApply from 2 December 2027, as amended in July 2026
High-risk, product-embeddedAI as a safety component of products under EU product law, such as machinery, lifts and toysApply from 2 August 2028, as amended in July 2026
Transparency obligationsSystems that interact directly with people must disclose it; synthetic audio, image, video and text must be marked machine-readably as generatedUnder the Act’s general application date of 2 August 2026
General-purpose AI modelsObligations on the providers of the models themselvesIn application since 2 August 2025; from 2 August 2026 the Commission can fine model providers up to 3% of worldwide turnover or EUR 15 million, whichever is higher

Two of these rows touch most operators long before any high-risk assessment does. The transparency row reaches any company whose product talks to users or generates content for them.

The general-purpose model row sits underneath every company building on someone else’s model. The obligations rest on the model’s provider, but a buyer’s product inherits the model it is built on, which makes “which model, from whom, documented how” a commercial question and not only a technical one.

What should an operator entering the EU be able to answer?

An operator should be able to answer five things about its own system, because every conversation with counsel, customers or procurement starts from them. It does not need to hold the whole regulation.

  • The role the company occupies for this system (provider, deployer, importer or distributor), given that the same company can occupy different roles for different systems.
  • The tier the system sits in, and whether that is an assessment or an assumption.
  • The dates that govern that tier after the July 2026 amendment.
  • The documentation that exists today about how the system was built, tested and changed, which is the material every tier’s obligations draw on.
  • Who supplies the answers the company cannot produce alone: which counsel in which member state, engaged when.

Confusion to avoid: these are understanding questions, not compliance steps. The answers are what make the eventual legal work fast and not exploratory.

Operators underestimate the fourth one. The record of how an AI system was built, evaluated and changed is the same artefact set a good handover produces, so a system documented well enough to hand over is a system documented well enough to explain.

How does Foxnut Studios read the EU AI Act?

We read it as an operator. We work from Paris and Bengaluru and build AI systems into clients’ commercial operations, so the Act is not an abstraction to us. It arrives on dates we can read in the Official Journal like everyone else.

Our founders’ answer starts before the Act. We already held ourselves to high documentation and compliance standards, for an operational reason: the systems we hand over keep running without us, and every tool eventually needs maintenance, upgrades and small edits.

The time those take is inversely proportional to the discipline with which the decisions, frameworks and data flows were documented during the build. The same discipline keeps the work future-proof against new legislation, this Act included.

On disclosure, we practise radical transparency, because we want to be on the same team as our clients. Essentially everything is disclosed, with one exception: proprietary algorithms, agentic systems and assets we developed and own the IP to, whose inner workings stay closed. Even for those, the client receives detailed documentation of how the system works in their business context and how it complies with every regulation of the day.

On counsel, questions answered before are not re-sent. Every genuinely new question goes through our own counsel first, so what gets built is built the right way.

The line sits here. Our market-entry work treats regulation as operator practice: understanding which questions the Act raises for a commercial plan, and sequencing them, is commercial work. Determining what the law requires of a specific company is legal work, and belongs with licensed professionals in the target market.

An operator who arrives in Europe holding the five questions above, with documentation in hand, buys less of the second kind of work. That is the most useful thing a description like this one can do.

What makes us different is that the documentation is built in and not bolted on when a regulator asks. The people who sign the proposal do the work, there is one tier, and what we hand over is a system your team can both run and explain.

You can read about our consulting work first. If you are entering the EU and want to talk through those five questions against your own plan, that is worth five minutes with us before it is worth a lawyer’s hour. Start there.

Sources

  1. Regulation (EU) 2024/1689 (the AI Act), full text on EUR-Lex: Article 2 scope, Article 50 transparency, Article 101 fines, Article 113 application dates Retrieved
  2. Regulation (EU) 2026/1744 (Digital Omnibus on AI), amending the AI Act's high-risk application dates, on EUR-Lex Retrieved
  3. European Commission: AI Act policy page, application timeline as amended Retrieved

Foxnut Studios takes on work like this from Bengaluru and Paris. If you want to see how we do it before you talk to anyone, here is how an AI engagement is scoped and priced.