Weekly digest · 2026-W25

June 15, 2026 – June 21, 2026

7 entries · 42 min total · Foundations & Protocols (6) · Enterprise & Strategy (4) · Infrastructure & Economics (2) · Governance & Safety (1) · Industry Verticals (1)

Entries

Day 93 · June 21, 2026The Agentic AI Data-Centre & Power WallDay 85 showed the token is nearly free; Day 86 showed the rails are commodity. So what's left to be scarce? Electrons. The binding constraint on the agent economy isn't the model or the chip — it's the gigawatt.
Day 92 · June 20, 2026Agent Interop & the Protocol Stack 2.0One year on from MCP, models compressed to a ~3% tie and tokens down ~1,000x — so what's the moat? The rails.
Day 91 · June 19, 2026The Inference Economics StackDay 83 was the demand side of Agent FinOps -- your routing, caching and budget levers. Day 84 was the people who run the fleet.
Day 90 · June 18, 2026The Agent-Augmented Org ChartYesterday (Day 83) was the cost of running the fleet -- FinOps, tokens, the five levers. Today is the people: who actually RUNS the agents once 60-80% of the work is agent-handled.
Day 89 · June 17, 2026The Agentic AI Operating Model & Agent FinOpsDay 81 was the regulator's clock; Day 82 was the buyer's checklist. Today is what happens AFTER you sign -- you have to run, cost and scale the fleet you just bought.
Day 88 · June 16, 2026The Agentic AI Procurement PlaybookYesterday's playbook was the regulator's clock. Today is the mirror image: the buyer's side. Governance has stopped being an internal hygiene project and become a contract line item -- and the RFP is where it is caught…
Day 87 · June 15, 2026The EU AI Act August 2 Enforcement PlaybookH2 opens with the regulatory event the whole series has been building toward. August 2, 2026 is when the EU AI Act's next wave of obligations becomes enforceable -- and this year the date comes with a twist.

Takeaways of the week

Read compute deals in gigawatts, not dollars When a lab signs $35–50B, translate it: how many GW of secured power, and when does it energise? Announced capacity (ERCOT's ~438 GW of requests) is mostly phantom — the delivered gigawatts, gated by 4–7-year interconnection and 128–144-week transformer waits, are what actually cap how fast agent capacity can grow. Day 93
Make energy part of your cost-per-task The Day 83 FinOps unit (cost per successful task) now has a power floor underneath it. The Day 85 levers — model routing, prefix caching, FP8 — are not only cost optimisations, they are energy optimisations that keep you under the wall. Measure watt-hours per completed task, not just dollars. Day 93
Layer the three protocols — don't reinvent the wiring Use MCP for tool/data access, A2A for agent-to-agent delegation, and AG-UI for the user-facing surface. Adopting the stack means you can swap the model underneath (Day 85's cheap, fungible token) without rewiring — the wiring is the asset, so don't build a bespoke RPC you'll have to maintain alone. Day 92
Plant your flag while the rails are still open Publish one SKILL.md to the marketplaces, expose MCP entry points on your product so agents can call it, and register an A2A Agent Card so other agents can discover it. The asymmetry window — free to build on, open governance — closes around 2027 as revenue shares formalise. Day 92
Treat the serving stack as a product decision, not an afterthought. Pick the engine for your workload -- vLLM for fastest-to-prod, TensorRT-LLM for peak NVIDIA throughput, SGLang for prefix-heavy agents -- then turn on continuous batching, prefix caching and disaggregated prefill. For repetitive agent prompts that is often a bigger cost win than swapping the model, and it is entirely under your control. Day 91
Quantise to FP8 by default, and measure cost-per-successful-task. FP8 roughly halves cost-per-token at negligible quality loss; 4-bit can drop you to a cheaper GPU class; speculative decoding adds 2-4x on output-heavy work. But validate on your golden set -- a lower-precision model that fails more tasks can cost MORE per completed job. The metric is cost-per-successful-output, not cost-per-token (Day 83). Day 91
Draw the work chart, not the org chart. List the jobs-to-be-done, then assign a mix of human and agent capacity to each. Pick a human-agent ratio per function and name an 'agent boss' who owns each agent's behaviour. Structure around the work, not the functional silo. Day 90
Solve ownership before scale -- write the agent RACI now. For every agent, name who owns the outcome, the behaviour, the data/context, the security/identity, the cost, and the edge cases. 'Who owns the decision?' must be answered BEFORE an agent is allowed to act autonomously -- not after the incident. Day 90
Measure cost per outcome, not cost per token. Instrument OTEL gen_ai spans, tag every call by orchestrator, sub-agent, model and team, and divide spend by COMPLETED tasks. A token count without a business outcome attached tells you nothing about whether you're winning. Day 89
Wire the five levers before you scale -- and enforce them in code. Routing (70/25/5), caching/context discipline, budget caps + circuit breakers, required tags, and human-in-the-loop review. Right-sizing once is theatre; the savings only stick when the levers are automated and enforced at the gateway, not recommended in a deck. Day 89
Make 'show me your audit trail' your first RFP question. Score vendors on the 12-field log, model-version pinning, tiered HITL and tamper-evidence BEFORE you score features. A great demo on an un-auditable platform fails your next regulator and auditor review -- and the obligation lands on you, the deployer. Day 88
Buy the control plane; build only what's differentiated. Pick the registry / identity / governance plane that matches your identity backbone (Agent 365 for M365/Entra, Agentforce for CRM-grounded work, Claude/Cowork as the value layer, WSO2 or self-host for residency). Layer a regulated tier where you must; build only the proprietary skills that touch your unique data. Day 88
Hold two clocks -- and plan to the earlier one. Article 50 transparency, governance and GPAI penalties are binding on August 2, 2026. High-risk (Annex III) is probably deferred to Dec 2027 by the Digital Omnibus -- but only once it is published in the Official Journal, which hasn't happened yet. Build the high-risk pack on the original clock so a slipped Omnibus never catches you out. Day 87
Ship the live obligation first: disclose + watermark. Every public-facing agent needs AI disclosure at first interaction and machine-readable marking (SynthID-class watermark + signed C2PA manifest) on synthetic media -- now. This is the obligation most teams actually touch on August 2, and it's a days-not-months fix. Day 87

Viral and open-source picks

Starcloud -- the data centre that left Earth Day 93
Goose by Block (aaif-goose) Day 92
Llama.cpp -- the engine that drives cost-per-token to ~$0 Day 91
Agnt8x -- HR for the AI workforce Day 90
Agenttrace Day 89
MLflow 3.x Day 88
OpenCode Day 87

Watch list

Day 88: Sovereign AI & the Compute Map — once power and chips become the binding constraint, the gigawatt race goes geopolitical. Day 93
Day 87: The Agentic AI Data-Centre & Power Wall — the physical constraint behind Day 85's silicon race. Data-centre electricity heading to ~945 TWh by 2030, the gigawatt compute deals, orbital data centres on the drawing board, and why power — not chips or… Day 92
Day 86: Agent Interop & the Protocol Stack 2.0 -- one year on from MCP. How the connective tissue settled: MCP at ~97M monthly SDK downloads, A2A v1.x under the Linux Foundation with 150+ production orgs, and AG-UI converging on a shared event model -- the… Day 91
Day 85: The Inference Economics Stack -- the supply side of Agent FinOps. The silicon and serving layer (Graviton5, Trainium/TPU, vLLM/SGLang, quantisation, speculative decoding) that sets the cost-per-token your org's FinOps levers push against -- newly in… Day 90
Day 84: The Agent-Augmented Org Chart -- who actually runs the fleet. Team topologies, RACI and the new roles (Agent SRE, AI FinOps lead, Context Engineer, the human-review function) that a traditional org re-wires into once agents become coworkers, not tools. Day 89
Day 83: The Agentic AI Operating Model & Agent FinOps -- what happens AFTER you sign. Running, costing and scaling the fleet you just bought: model-routing economics, cost- and quality-SLOs at fleet scale, the Agent SRE + CFO view, and how the audit trail you… Day 88
Day 82: The Agentic AI Procurement Playbook -- how governance becomes a contract line item. Buyer checklists for SPIFFE/SVID identity, kill switches, C2PA/SynthID, Annex IV evidence and SLAs; the build-vs-buy decision for the control plane; and why 'show me… Day 87