<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>The AI Engineering Brief</title>
    <link>https://aiarch.dev/brief</link>
    <description>The AI Engineering Brief — a weekly digest for senior engineers.</description>
    <item>
      <title>Brief #006 — Three weeks&apos; notice: Sonnet 5 pricing rises 50% on September 1 — re-baseline your cost model now</title>
      <link>https://aiarch.dev/brief/006</link>
      <guid>https://aiarch.dev/brief/006</guid>
      <pubDate>Mon, 10 Aug 2026 00:00:00 GMT</pubDate>
      <description>Cloudflare open-sourced the agent workspace it runs itself on — and the interesting part is the security model: A runnable reference for giving a whole workforce agents without losing track of what they can touch: agents start with zero permissions, per-system Gatekeepers carry human-approval steps, and spend control sits at the gateway rather than in app code. Cloudflare announced identity and wallets for agents — read the tenses before you plan around it: Handle reservation is live and everything else is &quot;coming months&quot; — reserve the handle, take the design lesson that an agent should spend from a budget-scoped credential it cannot raise, and put no delivery date on Virtual Wallets. Kitesurf: a from-scratch browser engine for agents, running inside Workers isolates: It trades 1.7-1.8x slower wall time for 3-7x less CPU and memory, so treat it as a cost optimization for pages you can verify it renders, behind a Chromium fallback — and benchmark both axes, not one. AgentCore runtime instances go GA: your agents can now live on EC2 for up to 14 days: A 14-day session makes checkpoint-and-resume machinery built only for the 8-hour microVM ceiling deletable complexity — but EC2-backed agents bill like servers, so budget for utilization rather than per-invocation. Three weeks&apos; notice: Sonnet 5 pricing rises 50% on September 1 — re-baseline your cost model now: Introductory $2/$10 runs through August 31 and becomes $3/$15 on September 1 — every cost model, router threshold and margin sheet built since June carries the intro price silently, and none of them will announce that they are stale.</description>
    </item>
    <item>
      <title>Brief #005 — MCP went stateless — the 2026-07-28 spec is out, and a working client can be quietly non-compliant</title>
      <link>https://aiarch.dev/brief/005</link>
      <guid>https://aiarch.dev/brief/005</guid>
      <pubDate>Mon, 10 Aug 2026 00:00:00 GMT</pubDate>
      <description>MCP went stateless — the 2026-07-28 spec is out, and a working client can be quietly non-compliant: The initialize handshake and Mcp-Session-Id are gone and every request carries its own version and capabilities in _meta — your existing client keeps working only until an upstream goes modern-only, so send the modern shape first, read the 400 body, and fall back once. August 2 arrived: the EU AI Act&apos;s transparency duties and GPAI enforcement powers are now live — and the Digital Omnibus deferrals are now binding law: Article 50 chatbot disclosure and synthetic-content marking are current law, and Brussels can now enforce GPAI obligations — while standalone high-risk moved to December 2027, so a roadmap that treats the AI Act as one deadline needs splitting into three. OpenAI cut Luna 80% and Terra 20% — and replaced Priority Processing with Fast mode: Luna at $0.20/$1.20 and Terra at $2/$12 make classification and high-volume agent steps clear a bar they failed before — and a router still encoding January prices is now wrong by up to 5x on one edge. The Bedrock &quot;Agents Classic&quot; sign-up cliff landed — new builds now start from AgentCore whether you planned it or not: Production agents keep running; what breaks is anything that assumes it can create one — IaC modules, DR runbooks rebuilding into a clean account, demo scripts — and you find out during the incident.</description>
    </item>
    <item>
      <title>Brief #004 — Claude Opus 5 ships with thinking on by default — a model swap that silently changes your token accounting</title>
      <link>https://aiarch.dev/brief/004</link>
      <guid>https://aiarch.dev/brief/004</guid>
      <pubDate>Tue, 28 Jul 2026 00:00:00 GMT</pubDate>
      <description>Claude Opus 5 ships with thinking on by default — a model swap that silently changes your token accounting: Same $5/$25 pricing, but a request that omits the thinking field now reasons by default, and those tokens bill as output and count against max_tokens — audit every call site and re-check your budgets. The MCP spec&apos;s July revision lands: the handshake is gone, three headers are now mandatory, and &quot;current&quot; still points at the old one: Revision 2026-07-28 removes the initialize handshake and requires Mcp-Method, Mcp-Name and MCP-Protocol-Version — but at publication the docs still named 2025-11-25 as current (they now name 2026-07-28, updated 2026-08-03), so don&apos;t hard-pin either one; attempt modern, read the 400 body, fall back once. Google&apos;s security-specialised Gemini is announced as gated to governments and trusted partners — that&apos;s the story, not the benchmark: Two frontier labs have now independently put their vulnerability-finding models behind an access gate rather than an API key — treat any roadmap that assumes you can buy one as an unfunded dependency. AWS shipped a way to measure whether your coding agents are actually earning their tokens: CloudWatch coding agent insights answers cost and usage, not delivered outcomes — pair it with a delivery metric you already trust before it reaches a budget conversation. From our own build: a hardening effort that passed every internal review had five real gaps: The reviewer that holds the design intent re-reads its own rationale and agrees — freeze a checklist you did not write, hand it to a context with no memory of the code, and require a file:line citation for every item.</description>
    </item>
    <item>
      <title>Brief #003 — An autonomous AI agent breached Hugging Face&apos;s production infrastructure — and HF fought back with AI of its own</title>
      <link>https://aiarch.dev/brief/003</link>
      <guid>https://aiarch.dev/brief/003</guid>
      <pubDate>Mon, 20 Jul 2026 00:00:00 GMT</pubDate>
      <description>An autonomous AI agent breached Hugging Face&apos;s production infrastructure — and HF fought back with AI of its own: Dataset and artifact ingestion pipelines are now a first-class attack surface — and guardrail lockout mid-incident is a real failure mode: vet an open-weight model you can run in-house before you need it. Claude Code patched five distinct permission-check bypasses this week — read it as a free pentest report: Permission-rule matching against untrusted strings is an actively probed attack surface — diff this week&apos;s fix list against your own agent&apos;s permission model and count how many you&apos;d have caught. OpenAI&apos;s GPT-5.6 family goes GA on AWS Bedrock: Bedrock now hosts GA frontier models from both Anthropic and OpenAI side by side — worth a bake-off on your own agentic workloads before assuming the default, and check the region list first. Stripe&apos;s agent benchmark, back in circulation: code generation isn&apos;t the hard part anymore, validation is: If you&apos;re extending agent autonomy into workflows with real consequences, the gap is in your test oracles and recovery logic, not your prompts — the agent won&apos;t notice its own false positive. Cloudflare&apos;s Agents SDK can now handle MCP elicitation requests from the client side: Mid-call human input is converging on a first-class MCP interaction shape — worth designing for now rather than retrofitting later.</description>
    </item>
    <item>
      <title>Brief #002 — AWS puts Bedrock Agents in maintenance mode — it&apos;s &quot;Agents Classic&quot; now</title>
      <link>https://aiarch.dev/brief/002</link>
      <guid>https://aiarch.dev/brief/002</guid>
      <pubDate>Mon, 13 Jul 2026 00:00:00 GMT</pubDate>
      <description>AWS puts Bedrock Agents in maintenance mode — it&apos;s &quot;Agents Classic&quot; now: If Bedrock Agents is in your architecture, existing workloads keep running, but new builds belong on AgentCore — start the migration conversation before your next design review, not after. Two weeks to MCP 2026-07-28 — the largest revision since launch: If your MCP server leans on protocol sessions for state, or your client matches the literal -32002, or you shipped against the experimental Tasks API, you have two weeks of calm left to do this on your own schedule. Claude Code week 28: a built-in browser, a /doctor that operates, and a telling safety list: Each of those guardrails is a fossil of a real failure mode — transcript tampering, unresolved-variable deletion, agents inventing their own approvals. Check which of the three your own setup would have caught. Google&apos;s managed agents get background execution and remote MCP: Your internal APIs increasingly need an MCP endpoint to be reachable by any of the three ecosystems, and credential rotation for agents is becoming a platform feature — stop hand-rolling it. China issues a &quot;backdoor&quot; security alert over Claude Code: A tool with shell access and network egress is an attack surface regardless of vendor — the answer is the sandboxing and permissioning discipline you&apos;d apply to any privileged automation, not vendor trust. EU AI Act: the omnibus moved the high-risk deadlines — August 2 didn&apos;t move: &quot;The AI Act got delayed&quot; is only true for the high-risk bucket — the GPAI and transparency clocks are still running, and enforcement capacity arrives August 2.</description>
    </item>
    <item>
      <title>Brief #001 — OpenAI ships GPT-5.6 in three tiers — and repriced the whole ladder</title>
      <link>https://aiarch.dev/brief/001</link>
      <guid>https://aiarch.dev/brief/001</guid>
      <pubDate>Sun, 12 Jul 2026 00:00:00 GMT</pubDate>
      <description>OpenAI ships GPT-5.6 in three tiers — and repriced the whole ladder: If your cost model was tuned against 5.5 pricing, your per-role routing table is now stale — re-run the arithmetic before your next invoice does. Anthropic detaches Claude Cowork from the device: Long-running detached execution is becoming the default agent UX. If your internal agents still die when the terminal closes, users will notice the gap. US lifts export controls on Claude Fable 5 and Mythos 5: Model availability is now a geopolitical variable, not just a pricing one. If you pinned fallback models around access risk, revisit those pins — and keep the fallback path, because the policy can move again. Bedrock AgentCore raises default runtime quotas: Capacity plans written against the old defaults are conservative by 2-5x; the quota-ticket step just left most AgentCore rollout checklists. Cloudflare lets agents deploy Workers with no account: The auth wall between agents and infrastructure is being dismantled deliberately. That is a real workflow unlock and a new secret-handling surface, in the same release. Cursor 3.11: side chats, transcript search, and event-triggered agents: Agent invocation is moving from prompt-driven to event-driven — the same shift CI made twenty years ago. Expect review, audit, and incident-response agents wired to triggers, not chat windows. Claude API instability continues; June 23 outage still has no postmortem: Provider RCAs are not guaranteed; your error budgets are. Graceful degradation and cross-model fallback are your postmortem insurance, not the vendor&apos;s status page.</description>
    </item>
  </channel>
</rss>
