Stack Literacy Is the New Leadership Skill

Underneath the noise about agents, a new infrastructure stack is being assembled with billions behind it — the layer that lets agents actually do things in the world. We've watched this movie before: the shift to cloud from 2006, microservices after that. The new customer for infrastructure is the agent, and the builders who read the stack correctly will define the next decade. The catch: these aren't Lego bricks yet. They're Legos and wooden blocks all marketed as Legos, and nobody tells you which ones snap together.

Six layers, at very different maturity

• Compute and sandboxing — mature. Agents need a safe, isolated place to run code; the real choice is ephemeral versus persistent.
• Identity and communication — in flux. Giving an agent an email address is a pragmatic shim, not an agent-native protocol.
• Memory and state — early and real, but the frontier labs are building it in, which puts standalone memory vendors at risk unless portability wins.
• Tools and integration — the N×M problem; durable until, and unless, a standard like MCP truly takes over.
• Provisioning and billing — brand new; the trust layer that lets an agent acquire and pay for services.
• Orchestration and coordination — the biggest gap. Running fifty agents reliably, with fallback, cost controls, and audit, is still hand-rolled. Whoever solves this at infrastructure grade owns the most valuable position in the stack.

Three things that are true right now

Reliability compounds the wrong way — five primitives at 99% each is 95% end-to-end. Every shim you adopt is a lock-in bet. And agent sprawl is coming, exactly the way microservices sprawled.

Stack literacy is no longer just an engineering concern. When agents drive real business outcomes, a leader who can't tell a mature layer from a shim is guessing — and hoping the agent works is not a strategy.