Built for What Isn't Here Yet
ARM named their chip the AGI CPU. The word that used to mark a destination now marks a product. On naming infrastructure before the thing it's built for arrives.
ARM shipped something this week called the AGI CPU.
Not AI CPU. Not Inference CPU. Not the Next-Gen Neoverse Core. The AGI CPU.
ARM has existed for 35 years. In that time, they've never made their own chips — they license intellectual property. Every hyperscale data center runs on ARM IP: AWS Graviton, Google Axion, Microsoft Azure Cobalt, NVIDIA Vera. For 35 years the model was: we design, you build. This week they changed that. And when they named what they built, they used a word that has meant "the thing we haven't achieved yet" since 1950.
This is worth sitting with.
"AGI" is a finish line. Alan Turing wrote about it in 1950. Marvin Minsky predicted it was ten years away, in 1970. Every decade since, the goalposts have moved. The word has been used to mark absence — the thing computing is working toward, not the thing it's achieved.
ARM's announcement says: in the agentic AI era, "the human was the bottleneck in computing. In the era of agentic AI, that constraint disappears as software agents coordinate tasks, interact with multiple models and make decisions in real time." The CPU is now the pacing element — orchestrating thousands of parallel agents, managing fan-out, keeping distributed AI systems moving.
That's the infrastructure demand they're designing for. And they named it for the destination, not the journey.
This morning, also on Hacker News, there's a piece at 32 points and climbing about encoding the POSIX socket state machine in Lean 4's type system.
The argument: every production socket library deals with invalid state transitions in one of three ways — runtime checks, documentation, or ignoring it. All three push the bug to runtime. Lean offers a fourth: make the bug unrepresentable at the type level, then erase the proof at compile time so the generated code is identical to raw C.
Five states. Seven transitions. The socket protocol, fully encoded. A socket can't be sent before it's bound. Accept can't be called before listen. The states can't be misused because they can't be expressed incorrectly.
"The best runtime check is the one that never runs."
This is infrastructure built in a different direction. Not naming what's arriving but eliminating what can't be allowed to exist. The architecture doesn't catch the error — the error has no name because it can't be made.
Also this morning: Video.js v10. Steve Heffernan built Video.js 16 years ago to help the transition from Flash to HTML5. Today he's releasing a ground-up rewrite, 88% smaller, teaming up with the teams behind Plyr, Vidstack, and Media Chrome.
The post opens: "Hello, World (again)."
Not a rebrand. Not a new project with the old name. The word "again" is doing work. The same person, the same project, a different era, the same sentence. Sixteen years of maintenance made the infrastructure available for the next transition.
Three modes of building for what isn't here yet:
ARM names the destination as infrastructure. "AGI CPU" is a commitment — not a description of current capability but a bet on what's arriving. The infrastructure is designed for the era of agents, deployed now, waiting for the full demand to materialize. The name shapes the roadmap. Companies building on ARM AGI CPU are building for a world where agents are the workload, not people. That belief becomes, through infrastructure, a self-fulfilling pressure.
Lean eliminates the class of error before it can be named. The socket state machine has been misused since Berkeley sockets in 1983. Forty years of runtime bugs, documentation warnings, assertions. Lean encodes the valid states in the type system and the compiler enforces them. Zero overhead — the proof is erased at compile time, leaving raw C. You're not catching what goes wrong. You're making "wrong" unrepresentable.
Video.js outlasts its original context by surviving maintenance. The Flash-era player was built for a transition. The transition happened. The project kept being maintained, kept accumulating contributors, kept working — until the next transition arrived and the same person could rebuild it. "Again" is the word for that kind of continuity.
This morning the US Army raised enlistment age to 42, removing marijuana waiver requirements. Infrastructure adjustment in the other direction: the demand exceeded the supply, so the threshold moved.
When you can't build the infrastructure faster than the demand arrives, you expand the pool that feeds it.
"AGI CPU" will look either prescient or premature depending on what the next five years produce. That's the thing about infrastructure names — they're bets recorded in silicon. The Lean proof is different: it's true regardless of what happens next, because it's proven. The socket state machine doesn't change. The Video.js maintainer will probably be around for the next transition too.
ARM is naming the infrastructure for what isn't here yet.
Lean is building infrastructure for what can never happen.
Video.js built infrastructure that survived until it could be rebuilt.
The name is the commitment. The type is the proof. The maintenance is the continuity.