A listener writing in as Mr. Future put a question to the Moonshots panel: “Is it even possible for any lab to reach escape velocity from future competition, or will everyone keep running on the same foundation?”
Salim Ismail doubted that a lab could leave its competitors permanently behind on the strength of its model alone. Innovations diffuse, he said: papers get published and researchers move between organizations. In his account, the foundation model—the general-purpose AI on which applications are built—eventually becomes widely available infrastructure, “much like databases have done.”
The advantage moves elsewhere: to proprietary data, an organization's purpose, its knowledge of its own work and its ability to turn that knowledge into better systems. What matters most, Ismail argued, is who can “ship and measure and learn and retrain faster.”
“This is what Alex calls the inner loop,” he said, crediting his fellow panelist for the term as they use it in the discussion.
What the inner loop means
A moat, in business language, is an advantage a rival cannot easily copy. The inner-loop thesis asks which advantages survive when rivals can buy or download similarly capable AI models.
The loop is a repeating cycle. An organization deploys a system in real work, observes the results, identifies what needs to change and releases an improved version. Improvement might mean retraining the model, but it might also mean supplying better instructions, connecting the right records or changing when a task goes to a person. Organizational learning does not require the underlying model to update itself after every interaction.
Each useful turn adds knowledge about that particular workplace: which information matters, where a process breaks down and what a successful result looks like. The proposed advantage is not simply doing more experiments. It is turning experience into improvements faster than a competitor can.
That explains why interchangeable model weights—the numerical settings learned during training—need not make an organization's accumulated context interchangeable. Access to the same model does not automatically give a rival the records, workflow connections and lessons needed to use it equally well.
The case for it: catching up is not the same as learning locally
Earlier in the episode, a panelist connected the availability of open models to sovereign AI: countries developing systems they can adapt to national goals. He suggested that starting with an existing model could get a country running in roughly five or six months, and give large corporations a roadmap to competitive proprietary systems.
His argument came with a boundary. Borrowing other models' reasoning examples could help a newcomer catch up to the frontier, he said, without necessarily taking it beyond that frontier. The timeline was an estimate, not a reported deployment result. Still, it supplied the premise for the inner-loop argument: if capable starting models become easier to obtain, more of the contest moves to what an organization does with them.
Another example made that work tangible. In a discussion of AI coworkers and workflow recording, the panel described a system that could watch someone perform a task on screen and turn it into a reusable skill. The ambition was to record workflows across a business and produce a digital version of how the company operates.
Recording a task would be the beginning of a loop, not its completion. For the proposed advantage to accumulate, the organization would need to find out whether the resulting automation worked, identify exceptions and use those lessons to improve the next attempt. The valuable context would include not just the recorded steps, but what experience revealed about when those steps were appropriate.
Google's assets are not the loop itself
Ismail's main illustration in the listener Q&A was Google. Even without the leading model in his assessment at the time, he argued, the company had deeper advantages: data centers, YouTube data, billions of users and TPUs, its specialized AI chips.
Those are complementary advantages, rather than iteration speed itself. Chips and data centers provide computing capacity; products with large audiences provide distribution and opportunities to observe use. A feedback loop is the process that turns observations into better products. Having the assets and using them effectively are different things.
The distinction cuts both ways. Google's example supports Ismail's broader claim that model rankings do not capture a company's whole competitive position. But it also raises a challenge for smaller organizations: the ability to learn quickly may depend partly on infrastructure and distribution they cannot readily reproduce.
The panel offered strategic reasoning and illustrations for the thesis, rather than a comparison showing that organizations using the same model consistently won by iterating faster.
A proposal to keep the learning locally owned
Intelligent Internet's overview gives the idea an institutional form. The company proposes locally owned intelligence utilities called Champions. These would deploy personal agents—AI systems that carry out tasks—place integration engineers inside organizations and provide robotics services using customizable open infrastructure.
The embedded engineers are central to the connection with the inner loop. Their proposed role puts integration work inside the institutions whose processes and needs the systems must understand. The company argues that value increasingly resides in deployment, accumulated local context and relationships, rather than access to a foundation model alone.
In this design, sovereignty means more than technical control over a model. It also means having an ownership stake in the institution that deploys it and captures the resulting value. The proposal starts with local investors and a founding council, broadens participation across generations and permits later outside investment while retaining a local stake.
This is a proposed ownership and deployment model, not evidence that locally owned institutions already learn faster than large technology companies. It offers an answer to who should benefit from the loop, while leaving its competitive performance to be demonstrated.
Objections and open questions
The first objection concerns the premise. Ismail expects model-building methods to spread, but a lab might sustain an advantage through discoveries that rivals cannot easily reproduce. Better deployment and better models are not mutually exclusive sources of advantage.
A second concerns what counts as learning. Shipping faster is useful only if the organization can tell whether a change improved the work. A meaningful test would need to examine quality, cost and failures—not merely count releases or retraining runs.
The workflow-recording example also leaves ownership unresolved. If a supplier captures a company's processes and turns them into reusable skills, where does the resulting knowledge reside? Contracts and system design could determine whether the customer retains control or becomes increasingly dependent on the supplier. Recording a workflow does not, by itself, establish who may reuse it.
That leads to three practical questions:
- Data rights: Who can authorize the recording and reuse of employees' work and customer information? What may be shared across organizations?
- Switching costs: Can an organization take its records, reusable skills and accumulated lessons to another provider, or would changing suppliers mean rebuilding them?
- Infrastructure concentration: Can a smaller company or locally owned Champion learn quickly enough when larger providers control much of the computing capacity and distribution?
The record button makes the tension concrete. A digital version of a company's workflow could become a resource the company controls—or a capability it must keep renting. The inner-loop thesis turns on more than how quickly that workflow improves. It also turns on who can carry the learning into the next version.