Grab the prompt kit I built to audit your AI platform lock-in — before your switching costs compound past the point of no return

Earlier this week, I wrote about Sam Altman winning a war he didn’t have to fight: the Pentagon deal, the $110 billion raise, the Stateful Runtime on Bedrock, the infrastructure geometry that gives AWS the enterprise agentic future while Azure keeps the stateless API. If you haven’t read that piece, go read it first. Everything here builds on it.

This piece is about what happened next: OpenAI engineers accidentally leaked the existence of GPT-5.4 by committing internal code to a public GitHub repo — twice, in five days — and the internet made it about the model. Prediction markets. Hype threads. “Generational leap” speculation. The usual cycle.

I don’t care about the model. Neither should you. And the explanation requires going somewhere that nobody in the AI discourse has gone yet, because it requires holding several technical concepts in your head simultaneously and most commentary can only hold one.

Here is the thesis: The company that first makes enterprise-scale context genuinely usable — not just stored, but retrievable, reasoned about, and acted upon across trillions of tokens — doesn’t just win the AI market. It becomes the new enterprise data platform. It subsumes the SaaS stack. It becomes the system of record for organizational knowledge in a way that makes Salesforce’s lock-in look like a magazine subscription. OpenAI is betting $600 billion in infrastructure that they can get there first. Anthropic may already be getting there by accident, through the organic weight of daily enterprise coding on Claude. And the thing that determines which approach wins is a technical problem that almost nobody is discussing: retrieval at a scale that has never existed in software.

Here’s what’s inside:

• What the leak actually tells you. Not the model; the sprint, and what it reveals about the problem better models alone can’t solve.

• The SaaS stack is a filing cabinet. Why the real value was never in data storage. It was in synthesis, and synthesis is what AI does.

• The four things that have to work together. Intelligence, memory, retrieval, and execution — where the failure of any one collapses the entire play.

• The retrieval problem nobody is talking about. Why RAG can’t solve enterprise-scale context, and why whoever cracks this first has a lead competitors can’t even assess.

• The flywheel that eats everything. How comprehension lock-in compounds and what builders should do about it this week.

Let me show you why, starting with what the leak actually reveals.

Note: As of this writing (March 4, 2026), GPT-5.4 has not shipped. It exists internally at OpenAI — two auditable pull requests and a deleted employee screenshot confirm that — but there are no public benchmarks, no API availability, and no official announcement. The confirmed features from the code leaks are full-resolution image support and a priority inference tier. The 2M context window, persistent memory, and “generational leap” claims are unsubstantiated speculation. What follows is an analysis of strategic direction, not a prediction of what GPT-5.4 specifically contains.