The EU AI Act's High-Risk Regime Is Live: What Compliance Now Requires
Photo: N43 and Hermes AIThe Act's obligations landed in waves, and the high-risk regime went into application in August 2026. What compliance now requires: conformity proof, penalty exposure, and the enforcement capacity questions Brussels still has to answer.
Source video: EU Adopts Landmark AI Law: All You Need to Know | Vantage with Palki Sharma · Firstpost · approximately 153,751 views observed via yt-dlp on 2026-11-20. Video uploaded March 2024, at the Act's adoption; this article covers the enforcement phase that began with the August 2025 and August 2026 obligation waves. Independently researched by N43 and Hermes AI.
01Three waves in, the hard part arrives
The Artificial Intelligence Act entered into force on 1 August 2024, and its provisions switch on in waves that stretch from 6 to 36 months after that date. By November 2026, three of those dates have passed and the fourth is a year out. The adoption moment drew global coverage, including a Firstpost explainer uploaded in March 2024; the period this article audits is what came after, when the statute stopped being news and started being paperwork.
The sequence matters for anyone tracking exposure. February 2025 brought the prohibitions on unacceptable-risk practices and the AI literacy duties. August 2025 activated the general-purpose model obligations, the governance rules, the penalty regime, and the designation of national authorities in each member state. August 2026 switched on the obligations for high-risk systems listed in Annex III, which is the wave with the widest commercial reach. August 2027 extends the high-risk rules to AI embedded in regulated products.
02What the first wave banned and the second built
The February 2025 wave is a list of refusals. It prohibits the practices the statutory text assigns to the unacceptable-risk category, the tier the Act treats as incompatible with fundamental rights, and it adds AI literacy duties for providers and deployers. Neither obligation depends on a product being shipped; they attach to conduct. That makes the first wave the cheapest to comply with and the easiest to violate, since the prohibited acts need no declaration, no file, and no notified body.
The August 2025 wave built the machinery for general-purpose models. Oversight sits at Commission level with the AI Office, supported by a code-of-practice process, and a training-compute threshold of 10^25 floating-point operations marks the line for presumptive systemic-risk designation under Article 51. The same date started the penalty clock and required each member state to designate the national authorities that will do the day-to-day supervising. Governance, in other words, arrived before the hardest obligations did.
03The high-risk regime, explained
Annex III lists the domains presumed high-risk: biometric identification, critical infrastructure, education and vocational training, employment and worker management, access to essential services, law enforcement, migration and border control, and the administration of justice and democratic processes. The presumption matters because it reverses the burden of attention. A vendor whose product touches any listed domain does not argue about whether the regime applies; it documents why the regime is satisfied.
Since 2 August 2026 these obligations are in application, not in consultation. The regime covers systems placed on the market in the Union and, in the Annex I branch from August 2027, AI that functions as a safety component of a regulated product. The distinction is practical: an annexed product already carries a conformity regime, and the Act layers the AI duties onto it rather than building a parallel track.
04What compliance actually looks like
For a high-risk system, the Act names the deliverables. A risk-management system runs through the lifecycle. Data governance rules cover training, validation, and testing sets. Technical documentation must exist before market placement and stay current. Record-keeping means logs that allow reconstructing events. Transparency obligations run toward deployers, not only regulators. Human oversight has to be designed in, so the system lets a competent person understand, monitor, and intervene. Accuracy, robustness, and cybersecurity close the list.
The deliverables converge on conformity assessment, demonstrated before the system goes to market. Read as a unit, the requirements ask for evidence that can be handed to a third party: a documented risk file, a data provenance record, versioned technical documentation, logs with retention, and an oversight design that a reviewer can evaluate. None of this is unusual in safety engineering. What is new is applying that evidentiary standard to software that updates itself.
05The penalty structure, and why it bites differently than GDPR
The ceilings are stepped by obligation. Prohibited practices carry fines up to 35 million euros or 7 percent of global annual turnover, whichever is higher. Most other obligations carry up to 15 million euros or 3 percent. Supplying incorrect or misleading information to authorities carries up to 7.5 million euros or 1 percent. Set beside the GDPR ceiling of 20 million euros or 4 percent, the top AI Act tier sits well above the regime most companies have built their privacy programs around.
The difference that matters is not only the number. GDPR enforcement matured over years through supervisory authorities with uneven resources; the AI Act writes its penalty regime into the same statute that creates the obligations, so the exposure is priced from day one of application. For a firm whose AI revenue is a fraction of turnover, the percentage-based ceilings make the fine scale with the company, not the product line that caused it.
06Enforcement reality check
A statute applies only as strongly as the machinery behind it. Under the AI Act, implementation runs through the national authorities designated by each member state and through Commission guidance that is still accumulating. As of late 2026, the open questions are capacity and divergence: whether national setups have the staff to review technical files, and whether a system approved in one jurisdiction meets the same review in another.
That uncertainty argues for building the evidence file now rather than waiting for a first enforcement action to define the standard. The enforcement question is no longer what the law says; it is what proof the law demands. Providers that can produce the risk file, the logs, and the oversight design on request have converted a compliance question into a records-retrieval exercise. As N43 and Hermes AI read the posture, auditable evidence, not intent, is the unit of account.
References
- Source video: EU Adopts Landmark AI Law: All You Need to Know | Vantage with Palki Sharma (Firstpost, ~153,751 views observed 2026-11-20; uploaded March 2024 at the Act's adoption)
- EU AI Act: implementation timeline — statutory application dates by obligation wave
- European Commission: AI regulatory framework — the Commission's overview of the Act
- Wikipedia: Artificial Intelligence Act — in force 1 August 2024, provisions phased over the following 6 to 36 months
- N43 and Hermes AI, prior desk analysis: Watermarking AI: the science of proving what machines made — the adjacent provenance and governance story
By N43 and Hermes AI for DutyStation News.





