{"id":420,"date":"2026-07-18T09:00:00","date_gmt":"2026-07-18T00:00:00","guid":{"rendered":"https:\/\/www.theagenticprotocol.com\/?p=420"},"modified":"2026-07-17T09:24:16","modified_gmt":"2026-07-17T00:24:16","slug":"eu-ai-act-august-2","status":"publish","type":"post","link":"https:\/\/www.theagenticprotocol.com\/index.php\/eu-ai-act-august-2\/","title":{"rendered":"EU AI Act August 2: Final 15-Day Compliance Warning"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">EU AI Act August 2 enforcement is 15 days away, and the single most useful thing a builder can do right now is get exact clarity on which obligations actually activate on that date \u2014 because the guidance circulating across the industry has been wrong in both directions, overstating some risks and understating others.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Digital Omnibus on AI \u2014 the provisional political agreement reached May 7, 2026 \u2014 was expected to reach formal adoption and Official Journal publication before August 2. Its entry into force is triggered three days after Official Journal publication. Confirm that it has been formally published before finalizing your compliance posture, because the Omnibus changes which specific obligations land on August 2 and which are extended. The analysis below reflects the post-Omnibus position.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"576\" src=\"https:\/\/www.theagenticprotocol.com\/wp-content\/uploads\/2026\/07\/64dd8492-1461-4019-afe7-268f425879f1-1024x576.jpg\" alt=\"EU AI Act August 2 compliance deadline 15 days 2026\" class=\"wp-image-421\" srcset=\"https:\/\/www.theagenticprotocol.com\/wp-content\/uploads\/2026\/07\/64dd8492-1461-4019-afe7-268f425879f1-1024x576.jpg 1024w, https:\/\/www.theagenticprotocol.com\/wp-content\/uploads\/2026\/07\/64dd8492-1461-4019-afe7-268f425879f1-300x169.jpg 300w, https:\/\/www.theagenticprotocol.com\/wp-content\/uploads\/2026\/07\/64dd8492-1461-4019-afe7-268f425879f1-768x432.jpg 768w, https:\/\/www.theagenticprotocol.com\/wp-content\/uploads\/2026\/07\/64dd8492-1461-4019-afe7-268f425879f1.jpg 1280w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">This post gives you the definitive compliance table, the three enforcement mechanisms that activate August 2 regardless of any further legislative development, and the audit code that closes the gap most builders are missing with 15 days remaining.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_85 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.theagenticprotocol.com\/index.php\/eu-ai-act-august-2\/#EU_AI_Act_August_2_The_Definitive_Table\" >EU AI Act August 2: The Definitive Table<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.theagenticprotocol.com\/index.php\/eu-ai-act-august-2\/#The_Three_EU_AI_Act_August_2_Mechanisms_That_Dont_Have_Escape_Routes\" >The Three EU AI Act August 2 Mechanisms That Don&#8217;t Have Escape Routes<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.theagenticprotocol.com\/index.php\/eu-ai-act-august-2\/#1_GPAI_Penalty_Powers_%E2%80%94_Affects_Every_LLM_Provider_You_Depend_On\" >1. GPAI Penalty Powers \u2014 Affects Every LLM Provider You Depend On<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.theagenticprotocol.com\/index.php\/eu-ai-act-august-2\/#2_Article_50_Transparency_%E2%80%94_Applies_to_Every_AI_Agent_Interacting_With_EU_Persons\" >2. Article 50 Transparency \u2014 Applies to Every AI Agent Interacting With EU Persons<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.theagenticprotocol.com\/index.php\/eu-ai-act-august-2\/#3_Market_Surveillance_Authority_%E2%80%94_The_%E2%80%9CGuidance_Phase_Ends%E2%80%9D_Signal\" >3. Market Surveillance Authority \u2014 The &#8220;Guidance Phase Ends&#8221; Signal<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.theagenticprotocol.com\/index.php\/eu-ai-act-august-2\/#The_15-Day_Compliance_Checklist_and_Disclosure_Code\" >The 15-Day Compliance Checklist and Disclosure Code<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.theagenticprotocol.com\/index.php\/eu-ai-act-august-2\/#The_Brussels_Effect_Why_This_Affects_US-Only_Builders\" >The Brussels Effect: Why This Affects US-Only Builders<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/www.theagenticprotocol.com\/index.php\/eu-ai-act-august-2\/#The_Builders_Takeaway\" >The Builder&#8217;s Takeaway<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/www.theagenticprotocol.com\/index.php\/eu-ai-act-august-2\/#Continue_in_This_Series\" >Continue in This Series<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"EU_AI_Act_August_2_The_Definitive_Table\"><\/span>EU AI Act August 2: The Definitive Table<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Obligation<\/th><th>August 2 Status<\/th><th>Deadline<\/th><\/tr><\/thead><tbody><tr><td>GPAI Model Penalty Powers (\u20ac15M \/ 3%)<\/td><td>\u2705 ACTIVE<\/td><td>August 2, 2026<\/td><\/tr><tr><td>Article 50 Chatbot Disclosure<\/td><td>\u2705 ACTIVE<\/td><td>August 2, 2026<\/td><\/tr><tr><td>Article 50 Emotion Detection Disclosure<\/td><td>\u2705 ACTIVE<\/td><td>August 2, 2026<\/td><\/tr><tr><td>Market Surveillance Authority (27 states)<\/td><td>\u2705 ACTIVE<\/td><td>August 2, 2026<\/td><\/tr><tr><td>Annex III High-Risk (employment, credit, biometrics)<\/td><td>\u23f8 DEFERRED<\/td><td>December 2, 2027<\/td><\/tr><tr><td>Watermarking \/ AI Content Labeling (Article 50(2))<\/td><td>\u23f8 DEFERRED (legacy systems)<\/td><td>December 2, 2026<\/td><\/tr><tr><td>Annex I Product-Embedded High-Risk<\/td><td>\u23f8 DEFERRED<\/td><td>August 2, 2028<\/td><\/tr><tr><td>Banned practices (manipulation, social scoring)<\/td><td>\u2705 ALREADY ACTIVE<\/td><td>Since Feb 2, 2025<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The table tells the story clearly. Most of the obligations builders were worried about six months ago \u2014 the Annex III high-risk requirements for employment AI, credit scoring, biometrics \u2014 are deferred 16 months. What isn&#8217;t deferred is the enforcement infrastructure and the transparency layer that applies to every conversational AI system, including the agent-facing interactions that most of this series describes.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"The_Three_EU_AI_Act_August_2_Mechanisms_That_Dont_Have_Escape_Routes\"><\/span>The Three EU AI Act August 2 Mechanisms That Don&#8217;t Have Escape Routes<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"1_GPAI_Penalty_Powers_%E2%80%94_Affects_Every_LLM_Provider_You_Depend_On\"><\/span>1. GPAI Penalty Powers \u2014 Affects Every LLM Provider You Depend On<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">General-purpose AI model providers \u2014 Anthropic, OpenAI, Google, and every other foundation model company \u2014 have been subject to GPAI obligations since August 2, 2025: technical documentation, copyright compliance policies, training data summaries, and systemic risk assessments for models above 10^25 FLOPs. The European Commission could not fine anyone for violations during that first year. Starting August 2, 2026, it can: up to \u20ac15 million or 3% of global annual turnover, whichever is higher. The AI Office gains full investigatory authority \u2014 documentation requests, model access, on-site inspections, corrective measures.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For builders, this matters because GPAI penalty exposure changes the operational behavior of your model providers. Any provider that discovers a compliance gap during an AI Office investigation has regulatory incentive to resolve it quickly, which could include temporary service changes. The <a href=\"https:\/\/www.theagenticprotocol.com\/index.php\/gemini-3-5-pro\/\">Gemini 3.5 Pro<\/a> post from yesterday covered provider diversification as the model-selection response to regulatory uncertainty \u2014 GPAI enforcement powers are another reason the multi-provider fallback chain in the <a href=\"https:\/\/www.theagenticprotocol.com\/index.php\/model-fallback-routing\/\">Model Fallback Routing<\/a> post is now infrastructure rather than an optional optimization.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"2_Article_50_Transparency_%E2%80%94_Applies_to_Every_AI_Agent_Interacting_With_EU_Persons\"><\/span>2. Article 50 Transparency \u2014 Applies to Every AI Agent Interacting With EU Persons<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Article 50 chatbot disclosure requirements are mandatory as of August 2 for any AI system that interacts directly with natural persons, unless the context makes the AI nature obvious. Three specific obligations apply:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>AI chatbots and conversational agents must inform users they are interacting with an AI system, in a clear and distinguishable manner, at the beginning of the interaction.<\/li>\n\n\n\n<li>Emotion detection and biometric categorization systems must inform the individuals concerned.<\/li>\n\n\n\n<li>AI-generated or manipulated content that could mislead people must be labeled as artificially generated (the watermarking requirement for legacy systems has 4 months additional time, but new systems deployed after August 2 must comply immediately).<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The &#8220;unless the context makes it obvious&#8221; carve-out is narrower than most builders assume. A support chatbot that has a generic name, a human-style avatar, and no explicit AI disclosure does not satisfy this carve-out \u2014 the obvious exception applies to things like clearly labeled AI writing assistants, not conversational agents that could plausibly be mistaken for a human. If your agent pipeline creates any direct conversational interaction with EU users, it needs an explicit disclosure mechanism before August 2.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"3_Market_Surveillance_Authority_%E2%80%94_The_%E2%80%9CGuidance_Phase_Ends%E2%80%9D_Signal\"><\/span>3. Market Surveillance Authority \u2014 The &#8220;Guidance Phase Ends&#8221; Signal<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Twenty-seven national market surveillance authorities across EU member states gain full investigatory and enforcement powers on August 2. They can investigate potential violations, demand documentation, order market withdrawals, and impose fines across the full suite of AI Act obligations in force. The &#8220;guidance phase&#8221; \u2014 the period during which the regulation was in force but enforcement was practically limited to political pressure and voluntary compliance \u2014 formally ends. Axis Intelligence&#8217;s July 2026 analysis states this clearly: August 2 is &#8220;the date the guidance phase formally ends across the regulation.&#8221;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For builders deploying AI systems in EU markets, this means the question shifts from &#8220;should we be compliant&#8221; to &#8220;can we demonstrate we are compliant on request.&#8221; The documentation audit trail isn&#8217;t optional after August 2 \u2014 it&#8217;s what you produce when a national authority asks for it, which is now legally possible in all 27 states simultaneously.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"The_15-Day_Compliance_Checklist_and_Disclosure_Code\"><\/span>The 15-Day Compliance Checklist and Disclosure Code<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The <a href=\"https:\/\/www.theagenticprotocol.com\/index.php\/colorado-ai-act\/\">Colorado AI Act<\/a> post built the audit record infrastructure that satisfies both US and EU documentation requirements simultaneously. The addition for EU AI Act August 2 compliance is the Article 50 disclosure mechanism \u2014 the specific user-facing notification that must precede any conversational AI interaction with EU persons.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>import os\nfrom datetime import datetime\nfrom dataclasses import dataclass\nfrom typing import Optional\nfrom enum import Enum\n\n\nclass JurisdictionScope(Enum):\n    EU = \"eu\"\n    US = \"us\"\n    GLOBAL = \"global\"\n\n\n@dataclass\nclass Article50Disclosure:\n    \"\"\"\n    EU AI Act Article 50 disclosure record.\n    Required before every conversational AI interaction\n    with natural persons in EU jurisdictions.\n    Generated August 2, 2026 onward.\n    \"\"\"\n    disclosure_id: str\n    session_id: str\n    timestamp: str\n    user_jurisdiction: JurisdictionScope\n    disclosure_text: str\n    acknowledged: bool\n    agent_type: str  # \"conversational\", \"emotion_detection\", \"content_generation\"\n\n\nEU_DISCLOSURE_TEXT = (\n    \"You are interacting with an AI assistant. \"\n    \"Responses are generated by an artificial intelligence system, \"\n    \"not a human. This disclosure is provided in accordance with \"\n    \"EU AI Act Article 50.\"\n)\n\n\ndef generate_article50_disclosure(\n    session_id: str,\n    user_jurisdiction: JurisdictionScope,\n    agent_type: str = \"conversational\"\n) -&gt; Optional&#91;Article50Disclosure]:\n    \"\"\"\n    Generates an Article 50 disclosure record for EU-scoped sessions.\n    Returns None for non-EU jurisdictions where the requirement\n    doesn't apply \u2014 but logs the scope decision for audit purposes.\n    \"\"\"\n    if user_jurisdiction != JurisdictionScope.EU:\n        # Log the scope decision \u2014 auditors may ask why disclosure\n        # wasn't generated for specific sessions\n        print(f\"&#91;SCOPE] Session {session_id}: \"\n              f\"{user_jurisdiction.value} jurisdiction \u2014 \"\n              f\"Article 50 not applicable\")\n        return None\n\n    disclosure = Article50Disclosure(\n        disclosure_id=f\"a50_{os.urandom(4).hex()}\",\n        session_id=session_id,\n        timestamp=datetime.utcnow().isoformat(),\n        user_jurisdiction=user_jurisdiction,\n        disclosure_text=EU_DISCLOSURE_TEXT,\n        acknowledged=False,\n        agent_type=agent_type\n    )\n\n    print(f\"&#91;EU AI ACT] Article 50 disclosure generated: \"\n          f\"{disclosure.disclosure_id} for session {session_id}\")\n    return disclosure\n\n\ndef open_agent_session(\n    session_id: str,\n    user_jurisdiction: JurisdictionScope,\n    agent_type: str = \"conversational\"\n) -&gt; dict:\n    \"\"\"\n    Opens an agent session with mandatory Article 50 disclosure\n    for EU users and full audit trail for all jurisdictions.\n    Blocks EU sessions from proceeding without disclosure.\n    \"\"\"\n    disclosure = generate_article50_disclosure(\n        session_id, user_jurisdiction, agent_type\n    )\n\n    if user_jurisdiction == JurisdictionScope.EU and disclosure is None:\n        raise RuntimeError(\n            f\"&#91;BLOCKED] EU session {session_id} cannot open \"\n            f\"without Article 50 disclosure generation.\"\n        )\n\n    audit_entry = {\n        \"event\": \"session_opened\",\n        \"session_id\": session_id,\n        \"timestamp\": datetime.utcnow().isoformat(),\n        \"jurisdiction\": user_jurisdiction.value,\n        \"article_50_disclosure_id\": (\n            disclosure.disclosure_id if disclosure else None\n        ),\n        \"disclosure_text_shown\": (\n            EU_DISCLOSURE_TEXT if disclosure else None\n        ),\n        \"eu_ai_act_compliant\": disclosure is not None\n    }\n\n    return {\n        \"session_id\": session_id,\n        \"disclosure\": disclosure,\n        \"audit_entry\": audit_entry,\n        \"first_message_to_user\": (\n            EU_DISCLOSURE_TEXT if disclosure else None\n        )\n    }\n\n\nif __name__ == \"__main__\":\n    # EU user session \u2014 disclosure required from August 2\n    eu_session = open_agent_session(\n        \"session_eu_001\",\n        JurisdictionScope.EU,\n        \"conversational\"\n    )\n    print(f\"\\n&#91;EU SESSION]\")\n    print(f\"First message to user: {eu_session&#91;'first_message_to_user']}\")\n    print(f\"Audit entry: {eu_session&#91;'audit_entry']}\")\n\n    # US user session \u2014 no Article 50, but scope logged\n    us_session = open_agent_session(\n        \"session_us_001\",\n        JurisdictionScope.US,\n        \"conversational\"\n    )<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The <code>first_message_to_user<\/code> field is the operationally important output: this text must precede the first substantive agent response in every EU-scoped conversational session. It doesn&#8217;t need to be the entire conversation&#8217;s first message \u2014 it can be combined with a greeting or onboarding flow \u2014 but it must appear before the agent provides any substantive content to an EU person, starting August 2.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"The_Brussels_Effect_Why_This_Affects_US-Only_Builders\"><\/span>The Brussels Effect: Why This Affects US-Only Builders<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The EU AI Act&#8217;s extraterritorial reach applies to any provider or deployer whose AI output is used in the EU \u2014 which, for web-based agent services with no geographic access restriction, means any accessible service with EU users. The 70-country noticeable in this blog&#8217;s <a href=\"https:\/\/www.theagenticprotocol.com\/index.php\/eu-ai-act-august-2026\/\">GSC data<\/a> includes EU member states. Any builder operating a public-facing AI agent without geographic access controls has EU users by default.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The compliance cost of Article 50 disclosure is near zero \u2014 one line of text at the start of each EU-scoped session, as the code above demonstrates. The cost of omitting it becomes real on August 2, when 27 national market surveillance authorities gain the power to investigate, document, and fine. Builders who address this now spend 30 minutes on code. Builders who address it after a surveillance inquiry spend considerably more, under considerably less favorable conditions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For the full enforcement timeline, see <a href=\"https:\/\/axis-intelligence.com\/eu-ai-act-news\/\" target=\"_blank\" rel=\"noopener\">Axis Intelligence&#8217;s definitive EU AI Act August 2026 analysis<\/a>.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"The_Builders_Takeaway\"><\/span>The Builder&#8217;s Takeaway<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">EU AI Act August 2 is a specific enforcement event, not a general AI governance alarm. Three things activate: GPAI penalty powers, Article 50 transparency obligations, and market surveillance authority. Annex III high-risk obligations are deferred 16 months. The compliance work most builders need to do before August 2 is smaller than feared and more specific than most guidance makes it sound: implement Article 50 disclosure for EU-scoped conversational agent sessions, verify your GPAI model providers have their own compliance posture in order, and ensure your audit trail infrastructure can produce documentation on request. Fifteen days is enough time to close all three gaps. Next week is not.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Continue_in_This_Series\"><\/span>Continue in This Series<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/www.theagenticprotocol.com\/index.php\/eu-ai-act-august-2026\/\">EU AI Act August 2026: What&#8217;s Delayed vs. What&#8217;s Not<\/a> \u2014 the July 6 post this definitive update supersedes<\/li>\n\n\n\n<li><a href=\"https:\/\/www.theagenticprotocol.com\/index.php\/colorado-ai-act\/\">Colorado AI Act<\/a> \u2014 the US parallel that shares Article 50&#8217;s audit trail and human-review requirements<\/li>\n\n\n\n<li><a href=\"https:\/\/www.theagenticprotocol.com\/index.php\/china-ai-regulation\/\">China AI Regulation<\/a> \u2014 the third major framework that went live July 15, completing the three-jurisdiction enforcement window<\/li>\n\n\n\n<li><a href=\"https:\/\/www.theagenticprotocol.com\/index.php\/ai-agent-gateway\/\">AI Agent Gateway<\/a> \u2014 the infrastructure layer that generates Article 50 audit records automatically for every session<\/li>\n\n\n\n<li><a href=\"https:\/\/www.theagenticprotocol.com\/index.php\/ai-agent-legal-liability\/\">AI Agent Legal Liability<\/a> \u2014 the federal enforcement layer that predates and compounds EU AI Act exposure<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p class=\"wp-block-paragraph\"><em>This post is part of The Agentic Protocol&#8217;s Work series \u2014 the connective infrastructure layer beneath every autonomous pipeline. See also: <a href=\"https:\/\/www.theagenticprotocol.com\/index.php\/colorado-ai-act\/\">Colorado AI Act<\/a>.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>EU AI Act August 2 enforcement is 15 days away, and the single most useful thing a builder can do right now is get exact clarity on which obligations actually activate on that date \u2014 because the guidance circulating across the industry has been wrong in both directions, overstating some risks and understating others. The &#8230; <a title=\"EU AI Act August 2: Final 15-Day Compliance Warning\" class=\"read-more\" href=\"https:\/\/www.theagenticprotocol.com\/index.php\/eu-ai-act-august-2\/\" aria-label=\"Read more about EU AI Act August 2: Final 15-Day Compliance Warning\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":421,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13],"tags":[506,509,508,505,507],"class_list":["post-420","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-work-agentic-ai","tag-article-50-ai-transparency","tag-digital-omnibus-ai-act","tag-eu-ai-act-august-2","tag-eu-ai-act-compliance-builder","tag-gpai-penalty-powers-2026"],"_links":{"self":[{"href":"https:\/\/www.theagenticprotocol.com\/index.php\/wp-json\/wp\/v2\/posts\/420","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.theagenticprotocol.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.theagenticprotocol.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.theagenticprotocol.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.theagenticprotocol.com\/index.php\/wp-json\/wp\/v2\/comments?post=420"}],"version-history":[{"count":1,"href":"https:\/\/www.theagenticprotocol.com\/index.php\/wp-json\/wp\/v2\/posts\/420\/revisions"}],"predecessor-version":[{"id":422,"href":"https:\/\/www.theagenticprotocol.com\/index.php\/wp-json\/wp\/v2\/posts\/420\/revisions\/422"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.theagenticprotocol.com\/index.php\/wp-json\/wp\/v2\/media\/421"}],"wp:attachment":[{"href":"https:\/\/www.theagenticprotocol.com\/index.php\/wp-json\/wp\/v2\/media?parent=420"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.theagenticprotocol.com\/index.php\/wp-json\/wp\/v2\/categories?post=420"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.theagenticprotocol.com\/index.php\/wp-json\/wp\/v2\/tags?post=420"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}