The Orchestrator

Cost pressure is not an incident. It is weather. Every capability this book has described — memory that persists, skills that accumulate, sub-agents that fan out, systems that run always-on — has a marginal cost, and the pressure to add capability is constant because capability is what the system is for. The frontier is becoming a major component of the human economy — the five largest providers have committed roughly $630 to $700 billion in capital spending for 2026, with about $1.09 trillion in future data-center lease obligations — and that scale means the pricing environment will keep moving: promotions that vanish, price cuts that respond to competition, new tiers that change the routing math.¹³ That capital reaches the orchestrator’s invoice by two routes. Until the data centers it is buying come online, capacity is rationed, and rationing looks like the weekly limits of Section 15.2 — announced by a company that had called itself compute-constrained, in a month of repeated outages. When the capacity arrives, someone has to recover the cost of building it, and my reading of the 2026 price sheet is that the recovery happens at the flagship tier, where list rates have held, while the cheap tiers absorb the competition. The orchestrator re-runs the arithmetic periodically because the arithmetic changes.

The orchestrator is the person who knows what the system costs and why, and says so before anyone has to ask. Every practice above — triage, the cost record, routing, a budget that is a credential rather than a sentence — is a way of making the bill legible to the people who pay it. The alternative is the surprise invoice, and the surprise invoice is how delegated systems get turned off.

HQ 6 — Assembled. The human and AI each wrote portions of this chapter. I assembled, reviewed, and take responsibility for the whole; the voice and arguments are mine, and I know which parts are which.