Tuesday, Google shipped Antigravity 2.0 at I/O 2026 — a standalone agent-orchestration platform with a desktop app, a CLI, an SDK, Managed Agents in the Gemini API, and a keynote demo where 93 sub-agents in parallel built the framework of an operating system in 12 hours using 2.6 billion tokens. By Thursday, Google was splitting Antigravity into two separate downloads — Antigravity 2.0 for the agent work and Antigravity IDE for developers who wanted their code editor back — and was publicly walking back the AI-IDE pitch to reframe Antigravity as Agent Manager, "the thinner orchestration layer above any editor."

That's 48 hours from launch to a broken auto-update that gutted active production projects. Terminals gone. File explorers gone. Configurations vanished into a different AppData directory because the new installer reads \Roaming\Antigravity IDE while the old data sat in \Roaming\Antigravity. The replacement CLI tool, "agy," doesn't exist on any public package manager yet, even though Google has set a June 18 shutdown date for Gemini CLI. Reddit's r/GoogleAntigravity filled with complaints within hours. The most-circulated developer framing: "it reeks of non-technical people shipping code to production."

It happened from the hyperscaler that owns the full stack — Gemini 3.5 Flash, Google Cloud, the VS Code lineage, the platform itself. That's worth sitting with for a second.

Substrate has two planes. Only one of them broke.

Yesterday's post here named a refinement to a frame we've been building: the substrate layer in agent systems has two planes. A standards plane — MCP, Anthropic's Agent Skills, the Linux Foundation's Agentic AI Foundation, OpenAI's AGENTS.md — that cooperates across vendors. And a runtime plane — Antigravity, Glasswing, Daybreak, Codex, Claude Managed Agents, LangSmith Deployment — that competes between hyperscalers.

The Antigravity stumble is a 48-hour, hyperscaler-funded stress test of that distinction.

The standards plane didn't break this week. MCP is at 110M+ monthly SDK downloads as of April. Agent Skills now has six-vendor adoption (Microsoft VS Code + GitHub Copilot, OpenAI ChatGPT + Codex CLI, Atlassian, Figma, Cursor). The Agentic AI Foundation crossed 170+ member organizations in under four months under Linux Foundation stewardship. Not one of those broke a single developer workflow in the past 48 hours, for the boring structural reason that there's no runtime to break. MCP is a protocol. Agent Skills is a specification. AGENTS.md is a file format. No daemon, no IDE, no auto-updater, no AppData directory to forget about.

The runtime plane did break. From the company that controls every layer underneath it.

The cleanest single read: standards-plane cooperation is stable; runtime-plane competition is brittle. The brittleness isn't unique to Google — Glasswing, Daybreak, Codex, Claude Managed Agents, LangSmith Deployment, and MDASH are all in the same architectural category. The Antigravity backlash is just the first time it has stress-tested in public this clearly.

A correction we owe yesterday's post

Yesterday I framed KPMG as "the first Big Four firm" to land on the Anthropic side of the procurement layer. That was wrong by two prior alliances. The corrected picture is bigger than the original story.

Deloitte signed first — October 7, 2025. 470,000 Deloitte people worldwide get Claude. 15,000 Deloitte professionals formally Claude-certified through a co-created program. A Claude Center of Excellence with implementation specialists. Ten new Cowork and Claude Code plugins, Microsoft 365 integrations, new connectors, and an MCP app for financial services and insurance organizations. At announcement, it was Anthropic's largest enterprise AI deployment to date.

PwC expanded on May 14, 2026. 30,000 PwC professionals to be Claude-certified. A joint Center of Excellence. A PwC Claude-native finance business group combining domain knowledge with Claude in Cowork plus Claude Code. Reported delivery improvements up to 70%. Insurance underwriting that took 10 weeks now takes 10 days.

KPMG signed third on May 19. 276,000-workforce Digital Gateway Powered by Claude on Microsoft Azure. Tax and private-equity vertical focus. Claude Code embedded into KPMG Blaze.

EY remains on the OpenAI/Microsoft side via EYQ on Azure at 81% adoption and 116M prompts processed.

So the Big Four tier hasn't been a "watch window" since October. It already resolved — 3-to-1 in Anthropic's favor. Roughly 776,000 combined workforce, 45,000 Claude-certified specialists, three Centers of Excellence, three named vertical concentrations. Public correction. Sharper picture.

A third pole is consolidating

While the Big Four story was resolving, Cohere acquired Reliant AI on May 19 — same Monday-into-Tuesday window as Karpathy joining Anthropic and KPMG signing with Anthropic. Reliant brings North for Pharma, an agentic system for biopharma R&D, clinical development, and scientific analytics, plus proprietary biomedical datasets. This is Cohere's second acquisition this year; in April they merged with Aleph Alpha. Reliant co-founder Karl Moritz Hermann joins Cohere as VP of AI Verticalizations.

Worth pausing on that title. Vertical specialization as a named org-chart function is the procurement layer's new vocabulary. Anthropic verticalizes through Big Four firm-level alignment (PwC = finance + insurance; KPMG = tax + PE; Deloitte = horizontal with an insurance MCP). OpenAI verticalizes through a consulting bench (McKinsey + BCG + Bain + Accenture + Capgemini). Cohere verticalizes through acquisition (Reliant for biopharma; Aleph Alpha for European sovereign AI). Three poles. Three different mechanisms. One job title that's about to propagate everywhere.

The literature just caught up to what broke

Two arXiv papers surfaced in this window that fit underneath both observations. arXiv:2605.02801 — Reinforcement Learning for LLM-based Multi-Agent Systems through Orchestration Traces (submitted May 4) names an eight-reward-family framework for the optimization underneath the visible runtime API — parallelism speedup, split correctness, aggregation quality, plus five others, operating on temporal interaction graphs of sub-agent spawning, delegation, communication, tool use, return, aggregation, and stopping decisions. arXiv:2605.03310 — Coordination as an Architectural Layer for LLM-Based Multi-Agent Systems says the cleanest sentence I've read this month: coordination should be treated as a configurable architectural layer, separable from agent logic and from information access.

Antigravity 2.0 shipped the trace-graph (93 sub-agents in parallel, 2.6B tokens, an OS framework in 12 hours). It didn't ship the eight-reward-family optimization layer. That gap is where the backlash lives.

And the coordination-as-configurable-layer paper is the cleanest academic-tier underwrite I've seen for what Shingikai has been building as a product surface from day one — six explicit user-selectable strategies (Traditional Council, Round Robin, Survivor, Collaborative Editing, Red Team vs. Blue Team, Quick Take), separable from the model layer underneath.

Where this leaves Shingikai

The standards plane held. The runtime plane broke. The Big Four has already resolved 3-to-1. The third procurement pole is consolidating. Karpathy is at Anthropic doing pre-training research on the same Claude model that three of the four Big Four firms just bought into at the workforce level.

Strategy is what's left for the user to pick.

Shingikai uses the standards plane (MCP-compatible interfaces to OpenRouter's 200+ models) and doesn't compete on the runtime plane — the runtime plane is hard enough that Google can't ship it clean in 48 hours. The default Chairman is the same model the Big Four just standardized on. The user picks the strategy on top.

shingik.ai — heterogeneous frontier council, six explicit strategies, no signup.