The AI Brief

Anthropic's Claude platform experienced elevated errors beginning at 05:06 UTC on August 24, affecting Claude Mythos 5, Claude Fable 5, Claude Opus 5, and Claude Opus 4.8. The disruption extended beyond claude.ai itself, hitting the Claude API, Claude Code, and Claude Cowork, effectively every major surface through which businesses integrate the platform.

The status moved from Investigating to Identified in 21 minutes, between 5:06 and 5:27 UTC. Anthropic did not disclose the underlying technical fault in its status update. As of the latest available update, the incident remained open at the Identified stage.

The August 24 disruption is the tenth outage across eight consecutive days in August, on top of earlier disruptions in March, June, and July, a pattern that points to shared infrastructure strain rather than isolated model faults. Anthropic's status history records disruptions on August 16, 14, 7, and 6, with August 6 classified as a major outage. The clustering of incidents coincides with Anthropic's most aggressive infrastructure expansion phase, including the Riot Platforms compute deal and the Theseus Infrastructure joint venture, neither of which delivers live capacity in the near term. Claude Console and Claude for Government remained operational during the incident.

Disclosure: Claude, which generates this brief, is built by Anthropic.

Gemini 3.5 Pro is still unreleased as of August 23, 2026, more than three months after Google announced it at I/O on May 19. It has now missed three targets, June, mid-July, and early August, and has no model ID, no pricing, and no launch date.

As of August 23, Gemini 3.5 Pro is absent from every published model list on both AI Studio and Vertex AI. Developers who filed allowlist requests on Google's AI Developers Forum received responses redirecting them to their sales representative, without confirming or denying the model's existence.

Google reportedly scrapped and rebuilt the base model after it stumbled on coding, meaning the flagship pipeline was in worse shape than even pessimistic outside observers had priced in. Google's on-record line since July 16 has been that it is testing 3.5 Pro with partners. On August 5, Demis Hassabis stepped back to chairman of Google DeepMind and Alphabet chief scientist, with CTO Koray Kavukcuoglu taking day-to-day control and the Gemini roadmap as SVP reporting to Sundar Pichai. Fortune tied the leadership reshuffle directly to stalled models and missed deadlines. First covered in this series beginning Vol. I, No. 68.

On August 20, 2026, Google's A2A protocol formally joined the Linux Foundation-directed Agentic AI Foundation (AAIF), placing A2A alongside Anthropic's MCP under a single neutral governance and signaling an end to proprietary agent protocol silos.

The AAIF grew from 49 to more than 250 members in under a year and counts Platinum signatories including AWS, Anthropic, Block, Bloomberg, Cloudflare, Google, Microsoft, and OpenAI, creating an interoperable protocol stack that strengthens security patching, verification of data flows, and enterprise adoption.

Putting A2A alongside MCP and related projects could help push the industry toward more modular, model-agnostic AI systems, giving companies more flexibility to choose providers based on cost, performance, latency, or other needs. A2A handles communication between independent agents while MCP handles connections between AI applications and tools and data. A2A 1.0 adds features including multitenancy, protocol negotiation, and signed agent cards designed to strengthen enterprise deployment and identity verification. The practical consequence for operators: an agent pipeline built to AAIF standards today can swap underlying model vendors without rewriting integration glue.

OpenAI confidentially filed its draft S-1 with the SEC on June 8, 2026, with the public prospectus expected on SEC EDGAR in mid-to-late August 2026, roughly 15 days before any roadshow. As of August 9, the full document had not appeared publicly on SEC EDGAR. Under SEC rules, the registration statement must be made public at least 15 days before an IPO roadshow begins. That 15-day rule means that a September roadshow, which Goldman Sachs and Morgan Stanley have been targeting for a Q4 listing, required a public filing by approximately today, August 24.

OpenAI is valued at $852 billion following its last funding round. Goldman Sachs and Morgan Stanley are leading the filing process ahead of a potential fall listing. The company reported more than $20 billion in annual recurring revenue for 2025 but internal documents project a $14 billion loss in 2026, with profitability not expected until 2029. Both OpenAI and Anthropic have confirmed the same broad stage: a nonpublic draft under SEC review, with no public prospectus or guaranteed offering date.

Investment bankers have advised both OpenAI and Anthropic that an early-mover advantage is at stake: the first to list would set the terms for how investors categorize the AI sector and gain access to enormous capital looking for an entry point. The filing's absence as August closes either signals SEC comment rounds are still running, normal for complex governance structures, or that OpenAI has made a deliberate choice to let September become its public filing month, targeting an October or November listing. First covered in Vol. I, No. 76.

Connecticut Governor Ned Lamont signed SB 5, the Connecticut Artificial Intelligence Responsibility and Transparency Act, on May 27, with an effective date of October 1, 2026. The Act requires deployers of automated-decision systems to conduct and document algorithmic impact assessments, disclose to affected individuals when AI is used in consequential decisions, and provide a mechanism to appeal or contest AI-driven outcomes.

The law applies to businesses that deploy covered AI systems affecting Connecticut residents, regardless of where the business is incorporated or headquartered, an extraterritorial reach modeled on California and Colorado statutes. Unlike Illinois SB 315 (first covered Vol. I, No. 41), which targets frontier AI developers specifically, Connecticut SB 5 covers downstream deployers: the enterprises integrating AI APIs into hiring, lending, or insurance workflows.

The legislative context includes the Trump Administration's export-control concerns regarding Mythos and Fable 5, suggesting state-level AI law is evolving in parallel with federal national-security framing rather than being displaced by it. With Connecticut and Illinois both now operative before year-end, and Texas, New York, and Colorado each at different stages of AI-deployer rulemaking, the window in which operators could treat US state AI law as theoretical has closed. The compliance surface is narrowing to specific documentation requirements, impact assessments, decision notices, and appeal records, that require process changes, not just policy updates.