If you opened a customer-service chat this morning and were told that you were speaking to AI, that notice sits inside a rule that already applies. If an employer buys an AI system to screen job applications today, the full set of AI Act requirements for that kind of high-risk system will not apply until December 2027. If the employer interprets that as permission to build first and think about governance sometime next year, however, the timetable has been badly understood. Both situations belong to the same law, but they sit at very different points in its implementation timetable. The EU AI Act has become harder to explain because it no longer has a useful single answer to the question “when does it apply?” The Regulation entered into force in 2024, some rules began applying in February 2025, obligations for providers of general-purpose AI models followed in August 2025, most of the Act became applicable in August 2026, and the 2026 Digital Omnibus then moved the detailed high-risk regime further into 2027 and 2028. Meanwhile, the Commission has published transparency guidance, enforcement has started, complaint mechanisms are operating, new prohibited practices are approaching their application date, and the first harmonised AI Act standard appeared in the Official Journal last week. A four-colour risk pyramid can still tell us something about the architecture of the law. It can’t tell a citizen what should happen when an AI system is used around them today, whether a company developing a system in 2026 can safely ignore requirements that apply in 2027, or why a European standard with the deeply unromantic name EN 18286:2026 suddenly matters. So we are going to leave the pyramid alone for a while. The more useful questions in October 2026 are what the Act already requires, what remains in transition, what people should notice when AI is used around them, and what organisations should be building now even when the legal deadline is still more than a year away. First, “provider”, “deployer” and “user” are not interchangeable Before looking at the dates, one piece of terminology is worth clearing up because it causes a surprising amount of confusion. Under the AI Act, a provider is broadly the organisation or person that develops an AI system or has it developed and places it on the market or puts it into service under its own name or trademark. A deployer is an organisation or person using an AI system under its authority. Personal, non-professional use is excluded from the deployer definition. That means an employee casually using an AI assistant, a company integrating an AI tool into recruitment, and the company that developed that tool do not automatically occupy the same legal position. Nor does a citizen asking a chatbot a question become a “deployer” simply by pressing Enter. The distinction matters because the Act distributes responsibility across the AI value chain. Providers may have obligations concerning how systems are designed, documented, tested and supplied. Deployers can have their own responsibilities concerning how systems are used, monitored and overseen in practice. In other words, buying an AI system does not magically transfer every governance question back to the vendor. Anyone who has ever bought enterprise software may recognise the general principle. The timetable now has several different clocks running The first substantial AI Act rules began applying on 2 February 2025. That included the original prohibited AI practices and the AI-literacy provision. Article 4 has since been amended by the 2026 Digital Omnibus, but it still requires providers and deployers to take measures supporting the development of AI literacy among staff and others operating AI systems on their behalf. What changed is that organisations are no longer required to guarantee some undefined “sufficient” level of literacy for every individual. The obligation is contextual: technical knowledge, experience, training, the way the system is being used and the people affected by that use all matter. That distinction is worth making because two equally unhelpful interpretations have circulated around AI literacy. One turns it into a universal certification exercise in which everyone needs the same course. The other assumes that the Omnibus quietly removed the obligation. It did neither. From 2 August 2025, obligations for providers of general-purpose AI models also began applying. Providers of those models have duties concerning technical documentation, information for downstream system providers, compliance with EU copyright rules and publication of information about training content. Providers of the most advanced models presenting systemic risk face additional risk-management, incident-reporting and cybersecurity requirements. Models already on the market before August 2025 have a longer transition period, until August 2027. For an ordinary organisation using a general-purpose model, that doesn’t mean it suddenly becomes the provider of the underlying model. It does mean that the AI Act is already regulating parts of the infrastructure on which many familiar AI products depend. The statement that “the AI Act doesn’t really start until 2027” is therefore simply wrong. Then came 2 August 2026, when the general application date arrived. Enforcement powers became operational for provisions already applicable, and Article 50’s transparency obligations began affecting the AI systems and synthetic content people are much more likely to encounter directly. The next important date is 2 December 2026, when the new prohibition introduced by the Digital Omnibus on AI systems generating non-consensual sexually explicit or intimate material and child sexual abuse material begins applying. The same date is also the end of the limited transitional period for the Article 50 machine-readable marking requirement for generative AI systems that were already placed on the market before August 2026. Then we reach the dates that have generated most of the confusion: 2 December 2027 for many Annex III high-risk AI systems, including systems in areas such as employment, education, essential services, migration and certain biometric uses, and 2 August 2028 for high-risk AI embedded in products covered by the legislation listed in Annex I. Those are not dates on which the rest of the AI Act suddenly becomes real. They are application dates for specific parts of the high-risk regime. That difference matters enormously. What should a citizen actually notice today? The most visible part of the Act in ordinary life is now transparency. Article 50 requires providers of certain interactive AI systems to make people aware that they are interacting with AI, unless that is already obvious from the circumstances. Providers of systems generating or manipulating synthetic content also have obligations to make those outputs detectable through machine-readable marking. Deployers have separate disclosure obligations for uses including emotion recognition, biometric categorisation, deepfakes and certain AI-generated or manipulated texts dealing with matters of public interest. These are related duties, but they are not the same thing. The visible notice telling you that the customer-service agent is artificial is there for a different reason from the machine-readable information embedded in synthetic content. One is about making the nature of an interaction clear to a person. The other helps technical systems identify content as AI-generated or manipulated. Deepfakes bring another layer. Where AI has generated or manipulated image, audio or video content in a way that could falsely appear authentic, the deployer may need to disclose that artificial origin. Artistic, fictional, satirical and similar works are treated more flexibly because transparency has to be provided without destroying the work itself. European law has, thankfully, not yet decided that every science-fiction film requires a warning across the actor’s… Get full access to REDefine // Civic Intelligence at associationredefine.substack.com/subscribe