The AI Act didn't push everything to August 2: transparency (Art. 50) and GPAI fines (Art. 101) took effect as planned — at AppH, zero lines of code to change, Chichi's disclosure already existed
The widely-covered delay of the "high-risk" section (Annex III, pushed back to December 2, 2027) created the impression of a general pause on the AI Act. That's not the case: Art. 50 (telling the user they're talking to an AI) and Art. 101 (fines for model providers like Anthropic, OpenAI, Google) took effect on schedule, August 2, 2026 — confirmed this week by TechTarget and Startup Fortune.
The timeline is now set in black and white. Regulation (EU) 2026/1744, the "Digital Omnibus" that delays the high-risk section, was published in the Official Journal on July 24 and entered into force on July 27 — it's no longer a political agreement, it's the law. The autonomous high-risk systems of Annex III (hiring, credit scoring, education, justice, critical infrastructure) now have until December 2, 2027; those embedded in products already regulated (medical devices, toys, elevators) have until August 2, 2028. But two articles haven't moved by a single day: Art. 50, which requires any AI system interacting directly with people to say so clearly, and Art. 101, the fines regime — up to 3% of global turnover or €15 million — for providers of general-purpose AI models (GPAI) like Anthropic, OpenAI, or Google who fail their obligations. Both took effect August 2, 2026, with no delay, confirmed by converging legal analysis (Gibson Dunn, White & Case, cited by Startup Fortune) and by the European Commission's own documentation.
At AppH, that makes for a quick, surprise-free audit. Art. 101 targets model providers — we're a deployer using Anthropic's Claude, not a GPAI provider, so these fines don't concern us or our clients. The Annex III delay changes nothing either: the audit we closed on July 19 had already confirmed that no AppManager module scores or classifies people (candidates, employees, students), so the result is identical whether the deadline is August 2026 or December 2027. The only article that genuinely concerns us as a deployer is Art. 50 — and there, direct verification in `landing/funnel.js`: the persistent subtitle in the Chichi widget's header (visible as long as the chat is open) and the very first message sent, in all 4 languages, already disclose "virtual assistant." It's not a message that scrolls past and disappears — it's displayed continuously. Zero lines of code to change before or after August 2.
For AppH
- Zero new compliance burden today: Art. 101 and its fines target model providers (Anthropic, OpenAI, Google), not AppH or its clients acting as deployers.
- The only article that genuinely concerned us (Art. 50, AI chat disclosure) was already covered before the deadline — verified directly in the code, not assumed: persistent subtitle + first message, in all 4 languages.
Against / what doesn't hold indefinitely
- This is a snapshot reading: if AppH ever added a voice or video agent without the same kind of explicit disclosure, the Art. 50 question would resurface — it's not an automatic, permanent protection.
- The Annex III delay doesn't mean the risk disappears forever: if AppH ever built a feature that scores or classifies people (candidates, employees, students), the December 2027 deadline would still apply — today's "nothing to do" reflects our current product choices, not a permanent exemption.
Today, part of the industry is going to use August 2 to sell urgency — "get compliant now." Our honest read is different, and this is exactly the kind of moment where we'd rather accompany than sell: if you're a deployer — like AppH and nearly all of its small-business clients — and not a model provider, Art. 101 and its fines don't concern you; the Annex III delay pushes most of the high-risk section back by just over a year; and the only genuinely actionable point today — Art. 50, telling the user they're talking to an AI — you probably already have if you use AppH, with nothing to change. We'd rather publish the article that says "you have nothing to do" than invent urgency to sell an audit. And whatever Annex III does or doesn't require yet, at AppH that doesn't depend on the regulatory calendar: our agentic modules — Automations/reminders, Messenger, Triage — always require owner approval before any action with real consequences, and as of this week, an emergency stop button to interrupt them mid-course (see yesterday's article). That's a deliberate product stance, not a box we tick to comply with a law.
Reviewed by a human at AppH