AI, three at a time · read · watch · listen

Tag

context-management

3 reads

Meta Engineering 2026-10-23-3

The Thin Orchestrator: How We Made Our AI Agents More Reliable by Giving the Router Less to Do

Meta's orchestrator is 1,300 lines, routes 20+ workflows to 14 subagents and does no domain work; only step 6 of its fixed 7-step protocol involves an LLM. A single agent hit 70-80% success with per-task manual prompts and 10-20% without, and column config prep fell from 3-4 days to under an hour (self-reported). It is the same move as 1Password's, applied to routing: the model gets isolated context to be creative in, and nothing deterministic is left for it to hallucinate.

The Atlantic 2026-05-18-1

AI Has Broken Containment

Wong's piece isn't a structural update — every event he cites is recycled public record from the past six months. What's new is that The Atlantic, NYT, Economist, Bloomberg, and Hard Fork have consolidated a unified "AI is no longer compartmentalizable" frame inside 30 days. The Cold War metaphor migration — containment, arms race, geopolitical actors — imports a specific policy menu (export controls, pre-release licensing, technology denial), and Anthropic and OpenAI will IPO into that frame, not the prior permissive one.

The Typical Set 2026-05-08-2

The bottleneck was never the code

Brooks 1975: software is the residue of human negotiation. For 50 years, tooling investment kept attention on the residue; agents collapsed the residue cost and exposed the substrate. The bottleneck moves from coders to spec-producers, which is to say management. Every AI productivity claim now needs a denominator that is not engineer-coding speed but spec-to-shipped cycle time. If management bandwidth is the bottleneck, individual agent productivity gains compound at zero, and you have just bought yourself the world's most expensive feature-bloat machine.