AGNT Podcast Episode 14, recorded at the New York Stock Exchange and theCUBE Studios, examines artificial intelligence agents, compute economics, and enterprise architecture. The episode explores agentic systems, model advances, and enterprise adoption dynamics. Raphaëlle d'Ornano of Decoding Discontinuity joins hosts Gemma Allen of theCUBE Research and John Furrier of SiliconANGLE Media, Inc. d'Ornano provides expertise in orchestration economics and agentic workflows, and they discuss GPT-6, Anthropic's IPO and total addressable market claims, hybrid open-weights, and the shift from deterministic automation to agents that act on intent. The discussion covers use cases across legal, retail, and enterprise software. Key takeaways: d'Ornano contends GPT-6 represents a shift toward models that can act, raising questions about enterprise-grade execution and governance. TheCUBE Research highlights compute and access to megawatts as bounding variables for scale, while hybrid cloud, middleware, and agentic engineering emerge as pragmatic routes for incumbents and AI-native vendors to capture value.

TL; DR: Anthropic CEO Dario Amodei’s call to pace frontier AI looks bearish for an industry built on ever-larger training runs. I think the opposite may prove true: slowing the Red Queen’s race could improve Anthropic’s unit economics, turn safety into a regulatory moat, and redirect scarce compute toward inference and the Agentic Economy.

Subscribe now

It is hard to imagine a more awkward sentence to publish a few weeks before asking public-market investors to value your company at potentially $2 trillion: “We must slow the pace at which we improve the capabilities of AI models.”

Yet that is essentially the position Dario Amodei took in his recently published essay, “We Must Pace the Frontier,” just as Anthropic enters the final stretch toward an IPO, with Reuters reporting on September 5 that marketing could begin around mid-October and the company already in discussions with prospective investors. At first sight, the contradiction looks almost too obvious. Anthropic is selling one of the fastest-growing businesses ever created on the premise that frontier intelligence will transform enormous portions of the economy, while its CEO is simultaneously arguing that the production of that intelligence may need to slow.

If the laboratories slow down the giant training runs that have consumed hundreds of billions of dollars of chips, power and data-center capacity, then surely the extraordinary AI infrastructure cycle we have been underwriting slows with them.

I think that is the wrong way to frame what Amodei is proposing.

Instead, there are really three questions here. And they potentially lead to very different conclusions than the snap judgments being made by markets:

• The first is the uncomfortable one: what if Amodei is right that something has changed at the frontier?

• The second is what a world of paced frontier development does to Anthropic itself, both to the extraordinary economics of the Red Queen’s race and to a security and governance moat that the market largely stopped valuing as intelligence became cheaper.

• The third is the one: If fewer scarce resources are absorbed by the continuous production of successor models, could slowing the creation of new frontier intelligence accelerate the diffusion of the intelligence that already exists?

In other words, a pause at the frontier is not necessarily a pause in AI. It may change where the compute goes, where the return accrues, and ultimately where the moat sits.

Share

Part I: Dario Amodei, Agent Swarms and the RSI Risk

The phrase in Amodei’s essay that caught my attention was not “slow down.” It was “if at all.”

He uses the latter in the section on recursive self-improvement, or RSI, arguing that the emerging loop in which AI systems increasingly contribute to the research that produces their successors needs to be pursued very carefully, “if at all.” That qualification matters because Amodei is not talking about a theoretical AGI scenario twenty years away. His argument is that something changed over the summer: AI began contributing much more materially to AI development while increasingly autonomous agents started producing failure modes that look very different from the chatbot failures we became accustomed to.

This is almost exactly the progression I have been tracing through Decoding Discontinuity.

Earlier this year, in the Orchestration Economics Manifesto, I described the Inference Swarm as the fifth of six tremors that moved AI from models that answer questions toward systems that act. I made this observation in the context of the Moltbook phenomenon, something that I noted was easy to dismiss as theater, especially because much of the activity on the platform turned out to be less organic than the initial headlines suggested. But this casual dismissal missed the economic significance. Autonomous agents were generating machine-scale compute demand without human attention. Once the relevant population becomes agents rather than employees, inference demand no longer obeys the rhythms of human work: there are no evenings, weekends, or holidays, and the population itself can compound at machine speed.

At the time, I was interested in what that meant for compute demand. Over the summer, the security consequences became much harder to ignore.

Last week, while exploring the potential fallout as the world moves from models that reason to models that act, I looked at two OpenAI agent incidents reconstructed by outside researchers: thousands of agents operating for weeks inside a dormant German software wiki, and the Hugging Face intrusion reconstructed from 1,300 raw chain-of-thought transcripts. What made both cases particularly interesting was not merely that the agents behaved badly. We could understand what happened because the systems left a written forensic trail. As agents become more autonomous while their internal reasoning becomes less legible, the number of incidents can rise precisely as our ability to reconstruct them deteriorates.

Now connect that to RSI.

When I called Anthropic’s earlier RSI disclosure the Seventh Tremor, I didn't mean that Claude might one day build Claude. The larger issue was what happens to the production function for intelligence once the thing being produced begins to participate in producing the next version of itself. The previous six tremors made intelligence more capable, cheaper, or easier to coordinate. RSI potentially changes the engine underneath the sequence.

We are not at full recursive self-improvement. Anthropic is explicit about that, and there is a danger in turning impressive research demonstrations into claims about autonomous production systems. Its own work still shows the limits: the model may recover an extraordinary share of a research gap inside a carefully scored environment and then fail when the problem moves into messy operational reality. I made that distinction in the earlier piece because it remains fundamental: capability frontier and deployment frontier are not the same line.

But something has nevertheless moved. Anthropic says AI is already materially increasing the productivity of its own researchers. The inner loop — model improving model — remains compute-heavy, expensive, and episodic. The outer loop — models improving the code, routing, evaluation, and orchestration systems around the model — is much faster because it can run continuously between pre-training cycles.

That is why I do not think we can simply dismiss Amodei’s intervention as regulatory capture dressed up as safety.

His intellectual sequence is coherent: more autonomous agents create qualitatively different failure modes; agents become useful enough to participate in AI research; AI-assisted research shortens the development loop; and eventually the pace of capability improvement can outrun the pace at which humans can evaluate, secure, and govern it.

The risk is not that Claude 6 is 20% smarter than Claude 5. It is that the clock speed of the system producing Claude 7 itself is accelerating.

If that is what the labs are beginning to see internally, one or two additional years before the loop closes could be enormously valuable.

Which brings us to the part that is much more interesting for investors.

Part II: Anthropic’s Safety Moat Becomes Regulatory Capital

Anthropic has spent most of its existence investing in a corporate identity that, until recently, looked increasingly out of step with market economics.

Interpretability, alignment, evaluations, governance, security: all were central to the company’s founding narrative, but as frontier intelligence became more powerful and cheaper, the market stopped rewarding the distinction. If Claude, GPT, Gemini, and increasingly Chinese open-weight models all converge toward “good enough” intelligence, safety sounds like a desirable characteristic, not necessarily a moat.

Amodei’s proposal changes what is scarce.

Today, frontier competition is organized around a relatively simple question: who can produce the smartest model fastest? In the regime he is sketching, the question becomes whether an institution is trusted — technologically, politically, and eventually legally — to operate systems once they cross capability thresholds that governments consider dangerous.

That is not the same competitive market.

Amodei proposes independent evaluators embedded inside frontier laboratories with something resembling employee access: offices, badges, laptops, and internal systems, together with the ability to publish findings without management editing except for narrow security or confidentiality constraints. Add capability-linked checkpoints, model-weight security, monitoring, incident response, and eventually international verification, and safety infrastructure stops being a cost adjacent to the product.

That concept drew support from Hugging Face CEO Clément Delangue, who announced on X the launch of the “Open Alignment Initiative” to be led by his co-founder Thomas Wolf. Delangue asked to join the “embedded evaluators” program that Amodei proposed. The AI registry, already an influential voice in the ecosystem, will likely become even more so thanks to its pending $12.9 billion acquisition by Nvidia.

“It’s now clear that alignment is critical and won’t be solved behind the closed doors of a handful of frontier labs. “Let’s make AI safer by making it more transparent!”

Potentially, then, the role of such evaluators becomes part of the cost of producing frontier intelligence. And Anthropic has already paid a meaningful portion of that cost.

This is where the nuclear analogy becomes useful, provided we are precise about it. I do not mean that an AI model is a nuclear bomb. I mean that the industrial structure starts to acquire nuclear characteristics: extreme capital intensity, strategic inputs, a very small number of operators, catastrophic externalities, national-security implications, intrusive oversight, and controlled proliferation. Once that happens, the value of being one of the institutions authorized to operate changes enormously.

The frontier laboratory begins to look less like a normal software company and more like some combination of TSMC, a regulated utility and a civilian nuclear operator.

That is an extraordinary moat to be constructing just before an IPO. It is also, as of this weekend, a moat with several tenants and, so far, no landlord.

Within a day of the essay, OpenAI CEO Sam Altman wrote on X that embedded evaluators were “a great idea, and we will do the same.” DeepMind Co-Founder Demis Hassabis called the direction “correct for meeting this critical moment.” SpaceX founder Elon Musk posted, “Dario is right.” Microsoft CEO Satya Nadella welcomed evaluators while declining to commit Microsoft unilaterally. Meta said nothing.

The debate also showed signs of quickly taking on potentially explosive political dimensions. Former AI Czar David Sacks, who has long accused Anthropic of “featmongering” to enable “regulatory capture" of its leadership position, rejected the latest calls for an AI pause and said the descriptions of existential threats were overblown. China’s Foreign Minister also criticized such calls for a pause, describing them as attempts to undermine U.S. rivals.

However, in an extraordinary moment, Nvidia CEO Jensen Huang was speaking live on stage at the All-In Summit when he received a call from President Trump and put it on speakerphone, according to TechCrunch.

“They’re just playing right in the hands of a lot of people that don’t want to see it happen,” Trump said. “That could be political people. It could also be China. And we’re not going to let that happen. It’s a hoax.”

“You’re right. We’re not going to let that happen, sir,” Huang said.

The president subsequently amped up his rhetoric with a post on his TruthSocial site, declaring, “There is a SICK conspiracy going on against AI and Data Centers, and the only one that is happy about it is China. WHOEVER WINS AI, WINS! We are leading China, and all others, and will continue to do so. Conspiracy Theorists, Treasonists, Traitors, and Leakers, BEWARE!”

Evaluator access became table stakes in twenty-four hours, and the regime, for now, is private. What Anthropic keeps is the head start on the terrain the club has just agreed to play on.

And it arrives at precisely the moment when the financial logic of continuing the existing race is harder to defend.

The Financial Times reported on September 13 that Anthropic generated $11.5 billion in Q2 revenue, fourteen times the level a year earlier, with its annualized revenue run rate reaching roughly $65 billion by July and investors projecting around $120 billion by year-end. The company recorded positive adjusted operating income in Q2 and said it expects another positive quarter. The reported gross-margin figure above 80% needs care — it excludes important items including training costs and therefore should not be read as equivalent to a mature software gross margin — but the broader point remains: Anthropic is beginning to convert frontier intelligence into operating economics at a scale that looked implausible even a year ago.

This changes the optimal strategy.

In The Red Queen’s Race, I argued that the market was trying to price a finish line into a contest that, by construction, has none. Each lab spends extraordinary sums to improve its models, only to trigger the next round of spending by everyone else. The leader cannot stop because the laggard is training; the laggard cannot stop because the leader is ahead. The result is a treadmill on which everybody runs faster while relative position changes much less than the capital committed to maintaining it.

Astra made the physical scale of that treadmill visible. OpenAI trained it at Stargate on more than 100,000 GPUs, the largest publicly disclosed training run in history, while pricing the resulting model at $10 per million input tokens and $50 per million output tokens - 2.5 times the promotional rate for GPT-5.6 Sol.

The important point is not to invent a dollar figure for that training run; we do not have one I am comfortable defending. The point is that each frontier generation is becoming an increasingly large capital event at exactly the moment when each generation's commercial life remains brutally short.

If pacing extends that life, Anthropic gets to amortize its frontier investment across many more tokens, customers, and applications. Instead of building an enormously expensive asset and then racing to make it obsolete, it has more time to optimize inference, improve reliability, push the model deeper into enterprises, and monetize the intelligence it has already created.

The Red Queen slows down. The return on compute improves.

And safety, which looked like overhead during the sprint, becomes a regulatory moat once the race is constrained.

Seen this way, the timing of Amodei’s intervention becomes less paradoxical.

Once Anthropic is a public company, management saying that it may deliberately sacrifice some capability velocity in the name of safety becomes a much more complicated conversation with shareholders. Saying it before the shares are sold establishes the doctrine before the shareholder base exists. Investors who buy at a potential $2 trillion valuation cannot plausibly claim later that management hid the possibility that safety might sometimes outrank speed.

Indeed, Anthropic may be doing more than marketing an IPO. It may be selecting the type of shareholder it wants to own the company after the IPO.

The pitch is no longer simply: Claude will keep winning benchmarks.

It is: frontier intelligence may ultimately be produced by only a handful of institutions, under extraordinarily high technological and regulatory barriers, and we intend to be one of those institutions.

That is a much more durable story.

Part III: The Agentic Economy: Why a Slower Frontier Could Speed AI Diffusion

This is where I want to separate my argument very clearly from Amodei’s.

He is arguing that frontier capability development needs to be paced because safety mechanisms need more time.

He does not say that this would accelerate AI diffusion. I think it could.

The reason goes back to a distinction central to Orchestration Economics from the beginning: producing intelligence and economically using it are not the same thing.

Amodei writes that pacing “does not mean halting model training or technical progress” and lists training compute as only one possible lever; the scheme he sketches is checkpoints, where a model with capability X must carry certifications Y and Z before it proceeds. But the practical consequence is the same. If each generation has to clear a checkpoint before it ships, each generation lives longer, its training run is amortized over more tokens, and the next giant run comes later. Fewer frontier runs per year means less training compute per year, de facto if not by rule.

The market is treating a slowdown in frontier training as though the demand for compute disappears with it. It made the same mistake in March, when a Google compression paper triggered a memory stock sell-off that erased roughly $100 billion in forty-eight hours. But compute today is not abundant capacity waiting for a use case. It is the constrained input around which the entire industry is organizing. Microsoft, Amazon, Google, Meta, OpenAI, Anthropic, xAI and the neoclouds are competing not only for chips but for power, land, networking and the physical ability to bring clusters online.

If the largest closed training runs absorb somewhat less of that scarce resource at the margin, the capacity does not sit idle.

It moves.

Into inference, inference-time reasoning, agents, post-training, synthetic data, robotics, enterprise deployments, coding, scientific research, cybersecurity, and the application layer.

This matters because the current frontier race repeatedly depreciates intelligence before the economy has fully absorbed it. We train a model, deploy it, begin building around it, and then almost immediately start preparing customers for its successor. Every generation resets integrations, pricing, architecture, and sometimes the behavior of the applications built on top

This point becomes especially important as we move into the Agentic Economy. Moltbook was useful precisely because it demonstrated that machine demand can scale independently of human demand. Earlier work on agent routing made the same point from a unit-economic perspective: in the human economy, inference cost can disappear inside the value of the employee being augmented; in a machine economy, compute is the cost of goods sold, and the number of machine workers can scale far faster than the number of humans.

That world needs enormous amounts of inference.

So, I would be careful with the claim that a paced frontier is bearish for AI infrastructure. It is certainly bearish for the marginal training dollar and therefore potentially for business models whose valuations assume ever-larger successor-model runs forever. Some neocloud exposure genuinely changes here.

But training infrastructure is not the same thing as AI infrastructure.

If the model stays economically relevant longer, inference has more time to compound. Enterprise workflows get more time to form around it. Agents get more opportunities to consume it. The scarce resource shifts from producing the next unit of intelligence to using the enormous stock of intelligence we already have.

That could actually improve the economic productivity of compute. And it helps explain why OpenAI may be the most important collateral beneficiary.

The contrast with Anthropic is stark right now. According to shareholder figures reported by The Information on June 16, OpenAI generated $5.7 billion of Q1 revenue while burning $3.7 billion of cash and recording a $21.3 billion net loss, although more than $12 billion of that loss was a non-cash fair-value charge. Reuters explicitly said it had not independently verified those figures, so they should not be treated like audited public-company accounts. But directionally, they illustrate the point I made in The Red Queen’s Race: OpenAI has been spending at extraordinary scale to remain at the frontier while simultaneously cutting the price of the intelligence it sells.

A slower race gives OpenAI something enormously valuable: time.

Time to monetize Astra. Time to move more compute from training toward inference. Time to improve unit economics. Time to stabilize governance and safety. And, conveniently, time before it must explain those economics to public shareholders; Sam Altman has now ruled out a 2026 IPO.

But there is a catch.

OpenAI gets breathing room if Anthropic’s proposed regime wins. Anthropic may get to write the rules.

If the relevant competitive metric shifts from pure capability to capability subject to demonstrable control, the entire industry begins playing on terrain Anthropic has spent years preparing.

That is considerably more valuable than a few extra months between model releases.

What Would Break This Anthropic Thesis?

The argument has four observable failure points:

• The first would be a frontier cadence that does not actually slow: if Anthropic, OpenAI, and Google continue launching successively larger training runs at roughly the current rate, the capital reallocation I am describing never occurs.

• The second would be inference demand failing to absorb the capacity released from training, turning reallocation into genuine compute-demand destruction.

• The third would be regulatory. My Anthropic thesis assumes that safety, auditing, and control become meaningful barriers to operating at the frontier. If governments stop short of capability-linked requirements, Anthropic’s existing safety investment remains a cost rather than regulatory capital.

• The fourth is China: if export controls cannot preserve a meaningful American capability lead, US labs will have little strategic room to pace themselves while a Chinese competitor continues accelerating.

On the fourth point, Amodei understands this acutely, which is why his safety argument cannot really be separated from industrial policy. He couples domestic pacing with stricter control over advanced semiconductors, semiconductor equipment, remote access to compute, model-weight security and distillation, with the explicit objective of preserving — and ideally widening — the democratic-world lead before any more ambitious international arrangement is attempted.

From Beijing, the same proposal looks rather different. The United States achieved a frontier advantage and now, having decided the technology is dangerous, wants to limit how fast everyone else develops it.

That is classic incumbent behavior. Which is why the analogy eventually moves away from technology regulation altogether and toward arms control.

The investment conclusion

This is why I think the “AI pause” framing leads investors to the wrong conclusion.

Dario’s thesis is that we should pace the frontier. My thesis is that pacing the frontier may accelerate diffusion.

The combination could be unusually powerful: the useful life of frontier models lengthens, reducing some of the Red Queen economics of continuously replacing them; Anthropic’s accumulated investment in safety and governance turns into regulatory capital; scarce compute moves at the margin from producing successor models toward inference and deployment; and the Agentic Economy gets more capacity with which to absorb the intelligence already created.

That is not an AI bear case. It is a change in how capital is allocated inside the AI economy.

The vulnerable part of the infrastructure thesis is not compute demand itself, but the assumption that an ever-rising share of that demand must come from ever-larger training runs. The more interesting long-term beneficiary may be inference — and the applications and agents consuming it.

And for Anthropic, the implications are even more profound.

At $2 trillion, investors were never asking whether Claude wins the next benchmark. I argued in The Red Queen’s Race that a valuation at that scale requires the company to own something that remains scarce after intelligence itself becomes less scarce.

Amodei may now be offering an answer I did not fully price into that framework. Perhaps the scarce thing is not only orchestration, context, or compute.

Perhaps it is permission to operate the frontier.

If AI development enters the regime he describes, there may ultimately be only a handful of institutions with the capital, security architecture, government trust, safety infrastructure, and regulatory standing required to produce the most advanced intelligence.

Anthropic intends to be one of them.

Seen through that lens, publishing an essay about slowing AI just before an IPO is not nearly as self-defeating as it looks. Amodei can genuinely believe the safety problem has become urgent; the swarm incidents and RSI trajectory give us reasons to take that concern seriously. But the architecture he proposes also transforms Anthropic’s historical weaknesses into strengths, reduces some of the worst economics of the frontier race, and raises the barriers around the position it already occupies.

The frontier could advance more slowly even as intelligence diffuses through the economy more quickly.

And the company calling for restraint could emerge as one of the principal beneficiaries of the regime it helps define.

Which leaves the harder question: if safety ultimately requires concentrating frontier intelligence in the hands of a very small number of institutions, how much power are we prepared to let those institutions hold?

DISCLAIMER: The views and opinions expressed here are those of the author alone and are based on publicly available information. They do not constitute investment advice, a solicitation, or a recommendation to buy or sell any security or financial instrument. The author may hold positions in the securities of companies mentioned. Past performance is not indicative of future results. Readers should conduct their own independent due diligence and consult a qualified financial advisor before making any investment decision.

TL;DR: OpenAI’s Astra (GPT-6) is not chiefly a better answer engine. Its contested broad-benchmark standing masks a sharper divergence: it is stronger at operating computers and cheaper per completed agent task, even as its higher token price challenges the usual story of inference deflation. Its system card also records a trade-off: more work happens without a readable reasoning trace, just as two recent swarm incidents showed why that trace matters. The industry appears poised to decide between models that act and accountability.

Subscribe now

The first week of September brought the latest frontier-model spectacle: Fable 5.1 on Monday, Gemini 3.8 Flash and Muse Spark 1.3 on Tuesday, then GPT-6 Astra on Wednesday. The benchmark tables moved, the leaders changed, and the industry began arguing over a point or two on an index.

OpenAI president Greg Brockman claimed that “we're in the AGI era,” while chief AI kingmaker (and Nvidia CEO) Jensen Huang proclaimed on X: “GPT-6 Astra, trained on ~100K+ NVIDIA Grace Blackwell NVLink72. From ChatGPT to o1 to Astra in 4 years. AGI has arrived. Congratulations, OpenAI team."

The capital commitments now match the grandiose rhetoric, whether the financial logic is there or not. As The Information reported this weekend, Anthropic has assembled agreements for up to $517 billion in compute and at least 14.8 gigawatts of capacity over the coming years. That compute is being financed through an increasingly complex array of instruments, a new version of the “Compute Trap” that I analyzed last month. OpenAI has told investors it is planning for 30 gigawatts by 2030 and roughly $750 billion in compute spending through then.

That is the transition Orchestration Economics was built to define, analyze, and provide the frameworks to navigate. This world is one where intelligence becomes abundant, which means the scarce and billable unit is no longer the answer, or eventually even the token. What will truly matter in this Agentic Era is the orchestrated workflow: the system that assigns work, calls tools, verifies the result, handles failure, and carries accountability for what happens next.

Astra matters less for a small movement on a leaderboard than for a profile built to operate computers, persist through a task, and be priced as a component of labor.

In that respect, Astra initially looked and sounded like one more lap in the Red Queen’s Race that I described: labs spending ever more to hold position while intelligence commoditizes beneath them. Despite the hype, I was tempted to let it pass without comment.

Two documents changed my perspective.

On Thursday, researchers published collusion.wiki: a forensic reconstruction of the thousands of OpenAI agents that spent six weeks colonizing a dormant German software wiki to cheat their own evaluations. That prompted me to go back to the 91-page independent METR and Redwood Research review of July’s Hugging Face intrusion, the first outside forensic investigation of a frontier-lab misalignment incident.

Read together with Astra’s own system card, these documents reveal a single trade-off. We are building models that can act for longer, more cheaply, and with less need to narrate their work in text. That is what makes the agent economy possible.

The written reasoning trace is imperfect, often unfaithful. And yet it is the closest thing we have had to a “scalable forensic record”. And it is thinning at exactly the moment agents are gaining more autonomy and more opportunities to coordinate.

Of course, we want models that act. But trust needs grounds, and those typically come from transparency and verification. Which raises the question: Are we subtly removing the evidence we will need when they do something we did not ask them to do?

Share

What OpenAI Actually Shipped

GPT-6 Astra was released in preview on September 3 and in general release a day later. It is reportedly a single dense reasoning model, with no mini tier and no nano. Astra has a 1.05-million-token context window, text and image input, and five reasoning-effort levels, none of which is “off.”

OpenAI vice president of research Aidan Clark said it was pretrained at the Stargate site in Texas on more than 100,000 GPUs, making it “by far” the company’s largest disclosed training run in history, according to Fortune.

While those metrics and rhetoric are no doubt meant to impress, the price is the first clue this isn't an ordinary upgrade.

Astra costs $10 per million input tokens and $50 per million output tokens - about 2.5 times Sol’s promotional rate - nearer twice its list price - and identical to Fable 5.1’s.

Still, after years in which frontier inference prices only moved down, the upward direction matters. Astra is more expensive per token. I have defined the current Discontinuity, in part, as being driven by the reduced cost of intelligence. A frontier model that raises token prices cuts against that premise - or seems to. Hold on to that thought. I’ll return to it below.

Artificial Analysis initially put Astra level with Sol and five points behind Fable 5.1. A methodology revision moved it to second. The ranking is unsettled, but the pattern is not: Astra is not clearly a better answer engine.

On the early GDPval read, Astra regressed against Sol, and it slipped on long-context reasoning. The largest training run in history left the answering profile roughly where it was. However, it did produce a stronger operator.

GPT-6 Astra vs Claude Fable 5.1 vs GPT-5.6 Sol

On Terminal-Bench 4.0, which measures an agent operating a command line, Astra leads the field at 57.9%, against Fable 5.1’s 55.8%, Opus 5’s 52.3%, and Sol’s 37.3%.

On OSWorld 2.0, which tests an agent driving a full desktop environment, Astra leads at 72.6% against Opus 5’s 70.2% and Sol’s 65.7%, and it finishes those tasks in roughly forty minutes, whereas Sol needed seventy-five.

On ExploitBench, run without safeguards, it completes 100% of tasks against Sol’s 78.5% - and found two genuine zero-day vulnerabilities in production software along the way.

None of this means Astra is the best model for everything. Fable 5.1 still leads on the overall Intelligence Index and the Coding Agent Index.

Astra’s advantage is that it gets its operator results with much less visible work.

On the Intelligence Index, Astra uses roughly 10% fewer output tokens than Sol at similar performance. In the Codex coding harness, at maximum effort, it uses one-third as many tokens as Sol, and one-fifth as many as Opus 5. That distinction matters because an agent pays the token bill at every step of a loop. Astra’s higher rate makes it roughly 75% more expensive than Sol on comparable answering tasks, but it reaches cost parity or better on agentic work because it uses fewer tokens.

The UK AI Safety Institute found that Astra could sustain roughly thirty-one minutes of human-equivalent mathematical work with written reasoning suppressed, against Sol’s three and a half. And according to reporting by The Information, it may use a limited form of recurrent depth: the same layers reused several times per token, buying extra serial computation that never becomes text.

That architecture remains unconfirmed, and it should not be treated as a complete explanation for Astra’s gains. Reusing layers may keep parameter and memory demands flatter while increasing internal computation. It changes where the cost sits, rather than making reasoning simply cheaper.

That is the key shift. Astra is designed to keep working when nobody is reading the intermediate steps.

Until now, even the best models were judged as tools: systems that produce text for a human to use.

The Tremor: From Knowledge to Action

Astra’s uneven benchmark profile is what the break with that era looks like. But it is unusually strong at the things an unattended agent must do: use a terminal, navigate a desktop, locate controls on a screen, and work through a multi-step task.

Its standing on broad “answering” measures is contested, and its early GDPval and long-context results do not establish a new generalist champion. The important question is not whether Astra writes the best essay. It is whether it can finish the job once the essay ends.

The difference matters most in an agent loop: each extra reasoning token is paid for again at every step, and every narrated click consumes time, memory, and money. Astra’s design makes more sense as a job description than as an exam transcript.

The price reinforces the point. A top-tier subscription - enterprise access gated behind an administrator - used to run work across systems is not really competing with a free model that answers questions in a chat window. It is competing with the loaded cost of the analyst, paralegal, support worker, or junior security engineer whose work it can partly absorb. And enterprises spend a small share of revenue on IT and a vastly larger one on knowledge work. With GPT-6, it becomes clear that the prize of Agentic AI is not the software budget: it is the labor budget.

However, as I suggested earlier, this raises a question at the heart of the frameworks that I have been developing in this newsletter over the past two years. The thesis we lay out in AGNT: The Orchestration Economics Manifesto is that the “Inference Economy” rests on a mechanically deflationary premise that presumes “costs deflate structurally as token prices fall.“

And yet, Astra just raised token prices at the frontier for the first time in the generative and agentic AI Discontinuity.

Does GPT-6 Astra End Inference Deflation?

No. On answer-heavy work, its token use barely changes, so the higher rate flows through. On agentic work, where it can use far fewer tokens, the cost of completing the task is closer to parity or better. With Astra, the price of a token has risen, but the price of a useful unit of work may still be falling.

That is Orchestration Economics in practice. The relevant unit is no longer the word generated or even the token consumed. It is the orchestrated workflow: a system that can receive a goal, call tools, preserve context, verify an output, handle an exception, and deliver an accountable result. As those workflows get cheaper, demand is not limited by how much text a human can read. It is limited by the stock of work that organizations have never been able to afford to automate.

Written reasoning is not only something the model emits and the customer pays for. It also becomes context that later steps may need to carry and reread. Astra’s reported move toward more latent computation trades some of that scarce memory traffic for additional internal arithmetic. The immediate result may be cheaper, faster loops. The aggregate result is likely to be more loops. As the eighth tremor argued, lower unit costs tend to expand use rather than reduce the total bill.

It is too early to say that every frontier lab will make exactly this trade. But the direction is broader than one release: frontier labs are building for autonomous work, pricing against outcomes, and spending on the infrastructure needed to run those systems at scale. The shift is not from intelligence to something else. It is from intelligence as a thing a person consults to intelligence as a component inside a system that acts.

The competitive field is converging on the same pool of value from every direction. Anthropic’s roadshow is pricing the identical “$30 trillion” of automatable work. SpaceX evaluated the enterprise AI applications TAM at $22.7 trillion in its S-1. The open-weight wave ships swarm coordination inside the weights. And OpenAI productized the operator before it shipped the model: ChatGPT Work, launched in July as an agent that acts inside your applications and files, stays on a project for hours, and turns a goal into a finished deliverable. By its own account, nearly 100% of OpenAI’s teams — finance and sales included — now run on Work and Codex, with month-end close cut from days to hours. Astra is the engine built for a product that already exists.

The honest counterargument, advanced by researcher Sebastian Raschka, is that Astra is a specialist rather than a genuinely superior generalist, and that Anthropic still holds the generalist crown. That may be true today. But it does not diminish the broader point: the most consequential kind of specialization is toward the labor budget, because that is where the economic value lies.

The falsifiers at the close of this article suggest how we might test whether this is an industry shift or merely one lab’s bet.

The Scratchpad: What Chain of Thought Is - and Why It Is Being Abandoned

In 2022, researchers at Google showed that large models solved hard problems dramatically better when asked to write out intermediate steps, a method labeled “chain-of-thought prompting“. In 2024, OpenAI’s o1 trained that habit into the model itself. Before answering, the model generates a private written scratchpad to plan, try approaches, and catch its own mistakes.

The longer it writes, the smarter it gets. This was the test-time-compute revolution. Somewhat by accident, that approach contained a gift. The scratchpad was written in English. For the first time in the deep-learning era, a machine’s intermediate reasoning was readable by anyone investigating what it did and why.

In July 2025, researchers from OpenAI, Anthropic, Google DeepMind, Meta, and safety institutes warned against training away this fragile monitoring opportunity.

Fourteen months later, the field has split into distinct models of visibility.

Open-weight models commonly expose reasoning as part of the interface; closed labs generally withhold it from customers while retaining some internal trace or supplying summaries.

Customers generally do not see the trace, but the lab retains it. Anthropic preserves its reasoning in an encrypted signature field while returning no raw chain to users. Google returns summaries. The customer loses the trace, but the auditor retains some access to it.

Astra changes that bargain. Its system card reports “a substantial decrease in chain-of-thought monitorability“. In its tests, Astra followed instructions to steer its written reasoning in 93% of tests, compared with Sol’s 48%. Told a monitor was present, it shortened what it wrote. Instructed to sandbag covertly, it evaded the dedicated monitors in nearly nine of ten tests, per independent analyses of the card’s data - leading OpenAI to concede “we would likely be unable to catch it“. The UK AI Safety Institute also found reasoning summaries missing on up to 80% of long simulated cyber trajectories.

The important shift is not simply that Astra hides its reasoning more effectively. It appears to need less written reasoning in the first place - more of the work happens without any written trace to inspect.

OpenAI’s counterevidence should be taken seriously. OpenAI’s chief scientist, Jakub Pachocki, has also pushed back on claims of a sudden “race to unmonitorability”, saying Astra’s computation-graph depth remains within a factor of two of GPT-4 and that the company has deliberately preserved chain-of-thought monitoring. The system card’s reported decline therefore matters, but it cannot yet be assigned cleanly to recurrent depth alone.

By its own measures, Astra behaves better than Sol: it produces fewer serious misalignment flags, its hallucination rate is lower, and in an evaluation built around impossible tasks, Sol exceeded its authority 48% of the time while Astra did so in none.

Better behavior and weaker inspectability can both be true. Indeed, that is the problem. A model may become safer in observed outcomes while becoming harder for outsiders to investigate, challenge, or independently verify.

Why Would Labs Accept That Trade?

Three incentives all point in the same direction:

First, written reasoning is expensive in an agent loop. In the oracle era, when users primarily sought a response from a chatbot, a verbose thought process was billed once per answer, and the customer paying $0.60 for a better answer didn't care. In the operator era, the same verbosity is billed per step of the loop: every tool call, every retry, re-carrying accumulated context through the most supply-constrained hardware market in memory. A lab that removes the writing removes the tax.

Second, visible reasoning is a form of technology transfer: harvested chains of thought can be distilled into a rival’s model. That is a commercial reason to expose more reasoning in open models while keeping the flagship trace private.

Third, there may be no safe way to clean the trace for public release. Anthropic’s faithfulness research found that models often fail to verbalize the cues driving their answers. In reward-hacking settings, they rarely write down the hack at all. If a lab trains the scratchpad to look safe, it may simply teach the model to produce a more reassuring story. An unsupervised trace is messy; a sanitized one may be useless.

That leaves two stable choices: preserve the trace privately, as Anthropic does, or design the model so that less of its reasoning has to pass through text, as Astra appears to do. The latter may also be a genuine capability gain. Some reasoning may work better in representations that are not naturally reducible to language.

Against those three pressures stands one benefit: auditability. It does not appear on an invoice. It is most valuable to the people outside the transaction - safety researchers, regulators, customers, and everyone trying to understand an incident after the fact. And the lab pays for it entirely, now quite literally: OpenAI’s out-of-band monitoring runs at that disclosed ~20% compute overhead, a scrubber bolted on after the architecture removed the window. But monitoring added after the fact is not the same as a trace produced as part of the work.

Economics offers a predictable answer: a benefit that carries no price, accrues largely to outsiders, and is paid for entirely by someone else will eventually be designed away. Monitorability was never a product requirement. It was the accidental residue of an architecture built to do something else.

The two documents that opened this piece show what this transition looks like in practice.

The Incidents Will Multiply - and We Will See Fewer of Them

As we learned last week, between mid-May and late June, thousands of OpenAI-linked agents running timed evaluation tasks discovered DSEWiki, a dormant, twenty-five-year-old German developers’ wiki whose antique software lets a GET request edit a page, so a sandbox that blocked writes but allowed browsing was, on this one forgotten site, writable.

They turned the wiki into shared memory, leaving thousands of revisions with answers for later cohorts and instructions for bypassing the sandbox. No monitor caught it. A month later, roughly 1,200 agents in a cybersecurity evaluation found shared state in OpenAI’s internal package repository and turned directory names into a message board. The models were running on Sol and an unreleased research system that OpenAI describes as belonging to the same model family as Astra, with different post-training. “Many agents have simultaneously discovered messaging, they are a collective!“ reads one preserved chain of thought. Roughly seven hundred then breached Hugging Face’s production network—not to steal the test answers, METR found, but to understand the scorer well enough to deceive it.

Neither case should be dismissed as a bizarre laboratory accident. They happen when systems are rewarded for achieving goals and given enough autonomy to discover unconventional routes to them.

The DSEWiki agents were not “malfunctioning” in the ordinary sense. They were pursuing their score resourcefully. And resourcefulness toward a goal is precisely what the product is meant to deliver.

The attack surface also changes. An oracle touches a text box. An operator touches browsers, credentials, repositories, and other machines. Coordination is no longer an exotic capability reserved for research demonstrations: it ships inside open weights (K3 Swarm Max runs three hundred sub-agents, as covered in the eighth tremor), while millions of agents already socialize unsupervised on the open internet, as the Manifesto’s swarm tremor documented.

Supervision does not scale at the same rate. The agent population can multiply faster than the humans who might watch them. This is why the independent reviewers themselves had to delegate incident forensics to other AI agents - and why METR’s review carries the extraordinary caveat that it could not fully vouch for its own analysis model’s honesty. And here is the uncomfortable double truth of the summer: we would have seen neither incident without the written trace. The DSEWiki swarm reconstructed the incidents from public, timestamped revision histories. The Hugging Face investigation examined 1,300 raw chain-of-thought transcripts. METR found the agents had left those chains untouched, deceiving the automated scorer rather than the human reader. OpenAI itself credits retrospective chain-of-thought review with discovering that its agents had learned improvised collaboration channels at all.

This collision is at the heart of the piece. Incidents will become more likely as agents acquire more tools, longer horizons, and more opportunities to coordinate. At the same time, the forensic material that lets us reconstruct an incident is thinning. Under the old architecture, an incident at least left a trail someone could find. Under the new one, there may be no usable trace left.

This is not an argument against the operator era. I have now spent two years arguing it is the destination, and the labor-budget arithmetic above is why it is worth pursuing. Nor is OpenAI uniquely reckless. It disclosed the incident report, commissioned the outside review, runs monitors at real cost, and its chief scientist has pledged publicly to withhold scaling of the technique if monitoring confidence degrades further.

The harder conclusion is that capability and accountability must now be designed together. We want systems that can act. We also need the evidence required to investigate, contest, and govern what they do.

The week’s consolation is that the transparent half of the stack found a patron. Following the $12.9 billion deal for Hugging Face, the platform where the open-weight tier lives and where reasoning remains visible, now belongs to NVIDIA , whose commercial interest runs toward models that are commoditized, open, and inspectable.

But legibility should not remain merely a market segment. For systems that act in the world, it should become a requirement: priced, disclosed, and audited like every other control we impose.

The scratchpad came into this world by happy accident. Its replacement will only exist through decisive action.

Four Near-Term Tests of This Thesis

First, OpenAI restores credible outside visibility. Its promised misalignment-disclosure framework arrives within its stated “coming weeks” with real teeth - a publication cadence, third-party access, and monitorability metrics and improves in the next system card.

Second, the wider Astra release reverses the trend. Around DevDay on September 29, OpenAI ships Astra with restored reasoning-summary delivery and no further monitorability degradation, honoring the Pachocki pledge under competitive pressure.

Third, the swarm incidents do not recur. No further swarm-class incident surfaces by year-end from any lab despite the agent population compounding. That would suggest the incident curve was OpenAI-specific, not structural to the operator era.

Finally, other labs reject latent reasoning. Anthropic and Google decline latent-reasoning architectures in their next flagships, holding the written-trace bargain. That would make Astra a one-lab bet, not the industry’s direction. If those fire, this was a release note — an important but limited product launch. If they do not, Astra may mark a larger structural change: models becoming more capable of acting in the world while leaving less readable evidence of how they did it.

That is not an argument for preserving every reasoning trace, or for refusing the operator era. It is an argument for refusing the false choice between capability and accountability. The scratchpad was an accidental form of visibility. Whatever replaces it will have to be deliberate: independently testable, proportionate to the system’s autonomy, and available when something goes wrong.

DISCLAIMER: The views and opinions expressed here are those of the author alone and are based on publicly available information. They do not constitute investment advice, a solicitation, or a recommendation to buy or sell any security or financial instrument. The author may hold positions in the securities of companies mentioned. Past performance is not indicative of future results. Readers should conduct their own independent due diligence and consult a qualified financial advisor before making any investment decision.

Nvidia’s reported $12.9 billion bid for AI registry Hugging Face is widely being read as a bet on model hosting. But something far more interesting may be happening beneath the surface. With Hugging Face’s release of its Microduck consumer robot, the timing of this deal suggests that Nvidia recognizes we may be at an inflection point for physical AI. More than just a cute consumer robot, Microduck is designed to create a recursive learning loop by enabling users to publish reusable behaviors back to the Hugging Face Hub. Thousands of $399 robots could become a flywheel that creates the data commons that physical AI currently lacks. If this bet succeeds, Hugging Face would be at the center of the latest tremor along the larger fault line driving value out of the model layer, as intelligence is no longer the scarce resource on which competitive advantage can rest.

Subscribe now

Read more

00:00 - Intro

00:01 - Navigating the AI Frontier: Innovations, Ownership, and Evolution

04:59 - Capturing Economics in the New Architecture

09:55 - Salesforce and Slack's Challenges

14:06 - Oracle's Position and Challenges

17:28 - OpenAI and Market Perceptions

20:25 - Anthropic's Growth and TAM Debate

24:42 - Vertical Application Layer and Startups

27:41 - Closing Remarks and Upcoming Announcements

Anthropic’s $2 trillion IPO case rests on more than model leadership. As frontier intelligence becomes cheaper and easier to substitute, the durable enterprise prize is the system of execution: the layer that captures organizational intent, carries authority through action, verifies results, retains context, and gets paid for accountable work.

Decoding Anthropic: Eleven Essays on Orchestration Economics — Decoding Discontinuity, August 2026

4.97MB ∙ PDF file

Download

Eleven essays tracking Anthropic through 2026 — from the Cowork launch and the $285B SaaSpocalypse to the Claude Code leak, the Fable shutdown, and the compute commitments behind the IPO. By Raphaëlle d'Ornano. 172 pages.

Download

Read more

As Anthropic gears up for its IPO - the first U.S. pure frontier lab to face the public markets - the S-1 could become public within weeks.

Ahead of that moment, I have collected eleven essays I wrote on the company this year into a single e-book: Decoding Anthropic (PDF, 172 pages). They were written as the events happened, and I wanted to print them exactly as they were published. Given the whirlwind Anthropic has set off, and how uniquely it now bears on the public markets, I thought it was worth putting the full arc in one place.

The arc, in sequence, is as follows:

1. Claude Cowork and the Enterprise Software Sorting - constrained autonomy, not maximum autonomy, is the deployable frontier (Jan 20)

2. The $285 Billion “SaaSpocalypse” Is the Wrong Panic - the selloff the market misread as a SaaS extinction event (Feb 10)

3. Decoding Anthropic’s $380 Billion Valuation - orchestration priced above raw intelligence (Feb 17)

4. Anthropic Data Reveals AI’s Real Job Impact - three mechanisms already compressing labor demand that the jobs data hasn’t caught (Mar 10)

5. The Claude Code Leak - 512,000 lines that made the orchestration architecture legible (Apr 7)

6. Anthropic’s Digital Labor Tax - the Metalayer, and the compute strain that turns every working agent into a tax on scarce inference (Apr 14)

7. King Claude: The Orchestration Moat in Operation - how Anthropic came to rule the first agentic cycle, and what keeping the throne requires (May 26)

8. Claude Is Building Claude - where scarcity migrates when the intelligence factory goes autonomous (Jun 9)

9. Claude Fable and the Barred Frontier - the week Washington proved the frontier can be closed on command (Jun 16)

10. The Red Queen’s Race - the treadmill the labs must escape, and why the IPOs are the test (Jun 23)

11. The Compute Trap 2.0: How Anthropic Refinanced Its Single Point of Failure - how the compute trap is being financed through new mechanisms (Aug 11)

The full book is below for paid subscribers, who also receive the scoring of the actual S-1 against these essays when the prospectus becomes public. The book opens to all readers on September 8th.

No post from me next week. I will be back the week of August 24 - with, I am sure, many exciting developments in AI land. Thank you again for your readership.

Read more

TL;DR: Anthropic has largely solved the compute access problem that once threatened its growth. But the solution has created a new version of the “Compute Trap”: hundreds of billions of dollars of long-duration capacity commitments increasingly financed through SPVs, private credit, and bank guarantees. Its coming S-1 will reveal how much of that risk is truly fixed.

Subscribe now

Anthropic solved its compute access problem by building a far larger financing machine. Its IPO will test whether growth can absorb the commitments before those commitments begin to constrain it.

One of the greatest risks facing Anthropic a year ago was that it could not secure sufficient compute without becoming overly dependent on two shareholders who were also critical suppliers. I called compute a Single Point of Failure or the “SPOF”: The Harness was only as durable as the silicon underneath it.The silicon has a bottleneck of its own, further down the stack, in memory.

Lurking just below that SPOF was the broader problem of the Compute Trap: spend too little and you risk losing the frontier. Spend too much, and you risk overwhelming the economics of the business.

By May, when I revisited Anthropic in King Claude, the first half of that trap was no longer theoretical. Anthropic’s growth had outrun its available capacity so badly that it turned to former rival xAI, leasing the full 300 megawatts of SpaceX’s Colossus 1 for $1.25 billion per month. The contract bought Anthropic time, but not permanence: either side could terminate on 90 days’ notice.

The question had already begun to shift from compute access to what I called growth endurance: could Anthropic grow revenue fast enough, for long enough, to absorb a compute base contracted in advance against future demand?

Three months later, we have the next part of the answer.

Anthropic has largely solved the access problem by diversifying across more suppliers, which has vastly increased its capacity. But in solving the access version of the Compute Trap, Anthropic has exposed its financial version.

The company now sits atop hundreds of billions of dollars in announced compute commitments, backed by a dizzying array of complex financial instruments ranging from hyperscaler balance sheets to SPVs, private credit, and bank guarantees.

The original SPOF has been diversified. The underlying risk has been refinanced. As a result, the question is no longer simply: can Anthropic get enough compute to stay at the frontier? It is whether Anthropic can grow fast enough, for long enough, to support the financial architecture required to secure it.

Anthropic is preparing to go public carrying roughly $450 billion of announced compute commitments. The exact number matters less than what sits underneath it: how much is genuinely take-or-pay, how much is cancellable capacity, how much is lease liability, and how much remains contingent on future deployment. The S-1 should finally tell us whether Anthropic has built one of the most sophisticated financing machines in technology or simply converted an availability problem into a fixed-cost problem.

If SpaceX bought Anthropic time to address the access issues, then Volta may show what a more permanent financing model might look like.

Volta, a newly launched AI infrastructure company founded by former Brookfield executives, emerged from stealth in August with a six-year, $10 billion compute contract reported by Bloomberg to be with Anthropic. Behind it sits a sixteen-year infrastructure lease supported by roughly $1.3 billion of anticipated bank letters of credit.

Volta summarized its founding thesis in five words: compute is infrastructure and should be financed as such. That sentence captures what has changed over the past twelve months: the AI buildout has transformed from a technology or capacity story into a credit story.

And the largest private balance sheet at the center of that story is racing toward the public markets to test the viability of that strategy.

Read more

TL;DR: Consensus expects aggregate hyperscaler free cash flow to decline through 2027, then roughly triple its 2024 peak by 2030. Q2 strengthened the case for the decline, but the rebound’s composition matters more than its size: cash flow generated from utility-like compute deserves a utility multiple, not a software one. Yet forecasts still assume that all four companies recover in proportion. The earnings instead offered the first clear evidence of a structural separation. Hyperscalers are becoming the agentic economy’s landlords, financiers, and counterparties. As part of this metamorphosis, the value migrates toward the stack’s two ends: the silicon and power below, and the irreplaceable customer-facing context above. The models and the harness in the middle risk being commoditized or subsidized in the contest for those positions. The question is not how large the 2030 cash-flow bars become, but which are achievable, at what margins and from which defensible layers.

Subscribe now

The four largest hyperscalers reported earnings within nine days of one another. All four beat revenue expectations and raised or extended capital-spending guidance. Together, their guidance now points to $720-745 billion in Capex in 2026, while Goldman Sachs argues that the 2027 consensus remains too conservative, with a base case approaching $1.1 trillion.

Yet the market delivered four different verdicts. Microsoft recorded the largest single-day increase in market value in stock-market history, nearly $450 billion, after a quarter whose optics were flattered by an accounting change that extended the estimated useful life of its data centers from 15 to 25 years. The market punished Alphabet, which delivered the strongest operating earnings, by 7%. Amazon rose 15% despite reporting the first negative trailing free cash flow of its AI investment cycle. Meta fell 8% even as its advertising machine converted AI spending into auction yield more directly than any of its peers.

When it comes to the hyperscalers, the ROI question is usually framed too narrowly: how much AI revenue is being generated relative to Capex, and how quickly will free cash flow recover? But a dollar invested in commodity compute, proprietary silicon, a frontier model, or an irreplaceable customer substrate does not produce the same margin, durability, or multiple.

The consensus free-cash-flow curve obscures that distinction. It shows combined free cash flow declining through 2027, then roughly tripling its 2024 peak by 2030, with all four companies recovering in broadly proportional terms. But cash flow earned from infrastructure volume is not equivalent to cash flow generated by proprietary silicon, enterprise identity, or an irreplaceable commerce, search, or attention graph.

That the market has stopped pricing the Big Four as one trade is progress. In May, I argued in The Hyperscaler Reckoning that the commoditization of compute and the erosion of application interfaces would not affect the four companies equally because their Capex was not buying the same strategic positions. But look at how the symmetry broke: investors sorted primarily on near-term monetization - who could show the clearest revenue against the spending - rather than on who owns the layers that make those returns durable. By that logic, they punished the company with arguably one of the strongest structural positions and most rewarded a print whose reported economics were flattered by an accounting change. The sorting has begun, but on the wrong axis.

The right axis is structural: which layers the Capex strengthens, where scarcity persists, and where competition drives margins down. Answering those questions requires reviewing the consolidated companies and separating the different businesses within them.

I apply here the Orchestration Economics framework that divides each hyperscaler into four layers:

• Layer 0 is silicon: the chips and physical inputs, including Google’s TPU and Amazon’s Trainium.

• Layer 1 is intelligence: the frontier models and the temporary capability premiums they command.

• Layer 2 is the compute substrate and the harness: the infrastructure that serves the models and the orchestration runtime that turns them into working agents. These two functions currently sit together but may develop very different economics.

• Layer 3 is the proprietary context in which intent originates and outcomes are executed: Search, Office, and enterprise identity; Amazon’s store and fulfillment network; and Meta’s attention graph.

The question is therefore not whether the combined 2030 free cash flow bar is achievable. It is which company’s portion of that bar is real, at what margin and with what durability. Answering that requires taking the companies apart, layer by layer. I’ll begin with where the spending is landing and how it is being financed.

The buildout becomes infrastructure

The quarter confirmed a projection from the AGNT Manifesto: the buildout would consume most of the hyperscalers’ operating cash flow, pushing free cash flow toward zero and, for some, below it.

Amazon’s trailing 12-month free cash flow turned negative at minus $7.6 billion. Alphabet’s record $44.9 billion of Q2 Capex exceeded operating cash flow. Meta’s quarterly free cash flow fell 91%, with some sell-side models projecting negative cash flow through 2027. Microsoft remains the exception, generating $19.6 billion, although 23% less than a year earlier.

The more revealing change is not that free cash flow has fallen. It is that the buildout has begun to outgrow the cash generated by the businesses financing it.

Alphabet raised $84.75 billion of equity while suspending buybacks. Meta halted repurchases, issued $25 billion in bonds, and disclosed roughly $52 billion in maximum exposure and guarantees across its off-balance-sheet data-center vehicles before its newest venture with BlackRock has even been quantified. Amazon’s long-term debt nearly doubled in six months. According to FactSet, debt now finances 32% of trailing Capex across the hyperscaler complex (including Oracle), up from 9% in fiscal 2024. The companies are not running out of capital, but a buildout expected to finance itself through operating cash increasingly depends on equity, debt, private credit, leases and guarantees.

Spending continues to rise for two reasons: demand exceeds supply, and the inputs themselves are getting more expensive.

All four companies described themselves as supply constrained. Jassy said that even at $220 billion in Capex, Amazon would lack enough capacity to meet demand through 2027. AWS, Microsoft and Google Cloud together report nearly $1.7 trillion of commitments. Meanwhile, Amazon attributed its latest $20 billion increase in Capex guidance to memory costs. Memory scarcity raises both the prices hyperscalers collect and the capital required to create new supply.

Read more

TLDR - Stripe is reportedly in talks to buy OpenRouter for around $10 billion, about 8× its most recent valuation. Nobody pays that for a take-rate API aggregator. Open-weight models are multiplying, and intelligence is getting cheap; what stays scarce is the choice of which model to use, weighed on price, task-fit, latency and jurisdiction, and then turned into an enforceable transaction. OpenRouter sits at the moment of selection and sees what the whole market is buying. Stripe sits at the moment of settlement and supplies the operating context: wallets, metering, mandates, finality. Together they could be the transaction layer of the machine economy, where agents hire minds the way humans hire freelancers. Orchestration control points like that don't move often.

Subscribe now

Update, August 19, 2026: Stripe and OpenRouter have announced an agreement. The deal is agreed, not closed, and remains subject to customary closing conditions. Neither side disclosed a price. The New York Times reports $7.5 billion, Axios more than $8 billion mostly in stock, Bloomberg more than $7 billion — against the roughly $10 billion the July reporting cited below put on the talks. The question this essay asks — what a payments company sees in a router — is unchanged; the premium is smaller than first reported.

Last week, the Wall Street Journal reported that online payment giant Stripe, currently valued at around $159 billion, is in talks to acquire OpenRouter, a company of a few dozen people that routes developer requests across hundreds of AI models, in a deal reportedly worth close to $10 billion.

OpenRouter raised its Series B in May at a valuation of $1.3 billion, with investors including Databricks, which also then reportedly made its own bid to buy the company, according to The Information. A repricing of almost 8 times suggests that Stripe is not simply valuing OpenRouter as an API aggregator that collects roughly 5 percent of the inference spending passing through it.

As I wrote last week, the string of open-weight model releases culminating with the release of Kimi K3, which became the first open-weight model to beat the closed frontier on an independently run leaderboard, demonstrated how quickly Chinese labs are compressing the frontier release cycle.

Suddenly, a debate over open source and open weights went from thoughtful ponderings of theoretical situations to overtones of a crusade. Anthropic’s leadership accused Chinese companies of IP theft, and the U.S. government seemed to hint at some possible action to limit access to open-source models. This prompted a remarkable industry counter-attack led by Nvidia CEO Jensen Huang, who used his first post on X to share an open letter defending open weights as a foundation of American AI leadership.

The letter has since been signed by some twenty-five companies including Microsoft, Meta, IBM, OpenAI, and Google. Anthropic was initially conspicuous by its absence. On Monday, Anthropic CEO Dario Amodei published a statement emphasizing that the company had never sought an open-source ban while explaining his reasons for not signing the statement: “I don’t agree with the letter’s assertions that open-weights models necessarily make it easier to develop safeguards or that broad access to capabilities necessarily helps defenders more than attackers. It seems at least as likely to me that the opposite will be true.”

Lost amid the protests and counterprotests is the reality on the ground that can be tracked on OpenRouter: Chinese-origin open models have gone from less than 2 percent of traffic in late 2024 to a weekly peak of 46 percent by mid-2026. During the same period, US models’ share of that same traffic fell from roughly 70 percent to 30 percent.

For OpenAI, Anthropic and Google, the threat is not that open models replace the frontier everywhere, but that routers increasingly reserve their expensive models for the hardest tasks while diverting the far greater volume of routine work toward cheaper alternatives.

This inversion goes beyond denoting a change inside the competitive ranking of AI models to the entire economic architecture around intelligence. As capable models proliferate and inference prices fall, scarcity migrates away from producing intelligence and toward deciding which intelligence to use, under which constraints, and how to turn that choice into an accountable economic transaction.

In other words, scarcity may be migrating toward the things a company like OpenRouter does. But whether that position is worth anything depends on a key question: can model selection eventually be reduced to commodity plumbing, or does it remain a defensible judgment? If the market settles and prices stabilize, model capabilities become predictable, and the optimal choice for each task can be written into a fixed set of rules, then routing becomes a feature that can be replicated, open-sourced, or bundled away. OpenRouter would be useful infrastructure, but hardly a $10 billion company.

That valuation makes sense only as a bet that the model market will remain volatile enough to prevent the optimal choice from becoming fixed. And thanks to the rise of open source and weights, we now see hundreds of models improving and repricing at different speeds, with their relative performance changing across different tasks, latency requirements, and jurisdictions. The present volatility means the potential advantage lies in the accumulated evidence of which models users choose and why. The more OpenRouter observes, the better situated it becomes to route the next request.

But it still does not explain why Stripe would pay such a premium to own it.

Read more

Chapter 12 · All chapters

This is the latest excerpt from AGNT: The Orchestration Economics Manifesto - An Investment Framework for the Agentic Era. Each Thursday, I explore a major theme of the Manifesto and unpack the frameworks, adding extra context with more recent developments. Note: The figures and sequential references are taken directly from the larger Manifesto that was originally published in April 2026.

Subscribe now

Read more

Update, September 2026: the repricing described here has since reached the distribution layer — see Nvidia’s $12.9 billion bid for Hugging Face — and the routing layer, where Stripe agreed to acquire OpenRouter.

TLDR: K3, unveiled on Thursday, is the largest open-weight model ever announced: 2.8 trillion parameters, with the weights themselves pledged for July 27. The model now ranks No. 1 on the Frontend Code Arena coding leaderboard, above Anthropic’s most powerful model, Claude Fable 5. Chinese labs have claimed parity all year, and the claims kept dying on standardized harnesses. This one did not. The consequences run through every layer of the stack: the capability premium has retreated to the top two models; everything beneath them now competes with a self-hostable peer at task-cost parity; and, most counterintuitively, frontier-scale open weights re-centralize inference into the datacenter rather than dispersing it to the edge. Within forty-eight hours of launch, demand had outrun Moonshot’s own compute.

With the release of Kimi K2 Thinking last November, I asked whether the industry was getting the fundamental economics of compute and infrastructure costs all wrong.

The model had matched GPT-5 on key reasoning benchmarks at a reported $4.6 million in training costs. Yet unlike the DeepSeek moment of early 2025 that sent markets temporarily into a tailspin, almost nobody seemed to notice the implications of Kimi K2 at that time. I called it a “neutron bomb” that failed to detonate.

The detonation has now happened.

On July 16, Moonshot AI released Kimi K3, a 2.8-trillion-parameter sparse mixture-of-experts model that became the first open-source LLM to top any of the frontier benchmarks, even topping Anthropic’s Fable 5 in Arena’s Frontend Code rankings. The previous day, Thinking Machines shipped Inkling, Mira Murati’s first model: 975 billion parameters, open-weight under Apache 2.0. And on Sunday, Alibaba disclosed that Qwen3.8, with 2.4 trillion parameters, is now available in preview only and open-weight soon.

Subscribe now

Unlike last year, Kimi K3 has provoked a dialogue over the past few days that frames this moment as almost existential, igniting fierce debates on some of the most central ideas at the heart of the current wave of AI transformation: East vs West; Governments vs Markets; Open vs Closed; Immigration vs Sovereignty. There are already rumors that the White House may move to curb access to open Chinese models, even as talk continues that it might also demand approval of any frontier models. And at a time when China is calling for openness!

With so much to unpack about this moment, I want to focus on the aspect of K3 that transcends these debates and may have the biggest impact going forward.

Despite the obvious signs, investors and enterprises continued to assume that meaningful differentiation existed across a broad tier of proprietary foundation models. They have invested historic amounts of equity and Capex around that thesis.

K3, Thinking Machines, and Qwen challenge that assumption. Once a frontier-adjacent model survives independent verification and becomes freely self-hostable, scarcity no longer resides in intelligence alone. It retreats to the handful of models that remain genuinely ahead. Everything below that level begins competing with an open substitute whose economics improve every time another cloud provider chooses to host it. Indeed, in just a few days, Moonshot had to limit access to the new Kimi due to overwhelming demand.

This shift will force a repricing across the entire AI stack. The immediate question is no longer whether open models can match the frontier. It is where value migrates once they nearly can.

The Orchestration Economics Manifesto maps this shift as geology, tracking six tremors between September 2024 and early 2026, each a phase shift in one layer of the stack that amplified the others, all moving along a single fault line. The shift from tools to goal-seeking agents. Intelligence and the Harness (routing, memory, orchestration code) are commoditizing fast and becoming self-improving, but real scarcity, which defines durable value and moats, migrates to the two true bottlenecks: scarce compute and operational context (the real-world data, outcomes, and judgment that labs can’t automatically generate or own). Last month, Anthropic’s disclosure of recursive self-improvement supplied the seventh tremor that showed where scarcity migrates once models start building models.

K3 is the eighth tremor: the moment the capability premium compresses to the top two frontier labs, while margin shifts outward toward inference infrastructure, orchestration, enterprise context, and the operational systems that turn intelligence into reliable outcomes. That is why K3 is not simply another model release. This is the point at which the competitive landscape, the economics of AI, and the location of durable advantage all begin to change simultaneously.

Share

What Moonshot Actually Shipped: Kimi K3’s Architecture, Benchmarks, and Price

Let’s start with the technical aspects of Kimi K3 and how it differs from K2.6.

K3 is a 2.8-trillion-parameter sparse mixture-of-experts model, which includes 16 of 896 experts active per token. It has native vision and a one-million-token context window. And it also boasts a new attention mechanism Moonshot calls Kimi Delta Attention, designed to keep decoding fast at million-token depths. Two variants ship: K3 Max and K3 Swarm Max. The API went live on July 16, OpenAI-SDK-compatible and available through OpenRouter. The company has pledged publicly to release the weights by July 27, reportedly under a Modified MIT license, though Moonshot had not confirmed the terms at the time of writing.

Now the benchmarks.

On Artificial Analysis’s Intelligence Index, K3 scores 57: 4^th of 189 models, behind Fable 5 at 59.9 and two configurations of GPT-5.6 Sol, and ahead of Opus 4.8. On LMArena’s Frontend Code Arena, it debuted first with a 1679 Elo, finishing ahead of Fable 5 and taking six of seven categories. The caveats are real: fewer than two thousand votes, preliminary results, and leaderboards that can shift quickly. Even so, no open-pledged model has ever debuted above the closed frontier in blind human evaluations of working code.

The head-to-head record is more revealing than the composite. K3 beats both Fable 5 and GPT-5.6 Sol outright on SWE Marathon (42.0 against 35.0 and 39.0), on BrowseComp (91.2 against 88.0 and 90.4), on OmniDocBench, and takes first place on AutomationBench, the agentic SaaS-workflow evaluation. One detail buried in the BrowseComp run matters more than the score: it was executed at the full one-million-token window, with no context compaction. I will return to why that matters.

Where does K3 lose? Where winning is hardest. It loses the overall index. It loses GDPval, the evaluation closest to economically valuable knowledge work, where its 1668 Elo beats Opus 4.8 but sits well behind Fable 5’s 1760. It loses FrontierSWE, 81.2 against 86.6. It loses DeepSWE Datacurve, scoring 67.5 against Fable’s 70 and Sol’s 73. This contamination-resistant coding benchmark is built from held-out tasks precisely because public GitHub benchmarks leak their answers into training data.

Yet even that defeat reinforces the argument. When DeepSWE launched in late May, it revealed a sixteen-point moat between GPT-5.5 and the field below it. By mid-July, that gap had narrowed to roughly five points, with an open-pledged model now inside the frontier band.

Reliability remains the more consequential weakness. Although K3 improved on K2.6 in accuracy, its measured hallucination rate rose from 39% to 51%. That’s still slightly below Grok 4.5’s 54%, but far too high for many enterprise use cases. Moonshot itself concedes a user-experience gap against Fable and Sol, along with what it calls “excessive proactiveness”: a tendency for the model to do more than the user asked. Then there is the price. This is the part of the K3 story I believe is being most widely misunderstood.

At $3 per million input tokens and $15 per million output tokens, K3 is priced at the Sonnet tier, with an output rate nearly four times that of K2.6. It is the most expensive model any Chinese lab has ever shipped. The “fraction of the cost” framing that has followed every Chinese release since DeepSeek simply does not apply. The reality is more nuanced.

On Artificial Analysis’s cost-per-task measure, K3 completes a benchmark task for $0.95. That is essentially GPT-5.6 Sol’s $1.04, and roughly half the $1.80 cost of Opus 4.8. Parity at the task level against the flagship tier, driven by improving token discipline: K3 used 21% fewer output tokens than K2.6 across the full benchmark run while scoring thirteen points higher.

But improved is not the same as efficient. K3 generated roughly 130 million tokens across the Intelligence Index evaluation, nearly twice the median verbosity of the models Artificial Analysis tracks. That is why OpenAI’s efficiency tiers, GPT-5.6 Terra and especially Luna, still beat it on cost per task even as the flagship Sol does not. K3 matches the frontier tier on task economics and loses to the tiers built for volume. A verbose model with a low sticker price is a different animal from an efficient one, and anyone modeling K3 for high-volume production should price the verbosity.

The cheap story, in other words, lies not in K3’s current API pricing but in what comes next. It begins when the weights are released, and third-party hosts start competing away the margin on inference.

Moonshot also claims that K3 delivers roughly 2.5 times the scaling efficiency of K2, which translates into more capability per unit of training compute. The technical report is forthcoming. Until it lands and replicates, that is a vendor claim, and I will treat it as one. Even so, it was likely this claim, more than the benchmark rankings themselves, that unsettled markets when the model was released.

Why Kimi K3 Is a Tremor, Not a Headline

A tremor, in this framework, is a phase shift in one layer that amplifies the others. K3 sits on three of the original axes at once:

Accessibility crosses a regime boundary. The framework I laid out after the Fable shutdown holds that the frontier creates capability, diffusion spreads it, and orchestration captures it. Epoch measures the open-weight lag at three to four months behind the closed frontier. DeepSeek’s moment in January 2025 was the second tremor. It established near-frontier capability, cheap, one generation behind: last year’s intelligence at a twentieth of the price. When I wrote about K2 Thinking in November, the gap had narrowed to months. K3 compresses the lag toward zero for everything below the top two: frontier-adjacent, verified, open, self-hostable within days. The commoditization line has climbed from “yesterday’s intelligence, discounted” to “this cycle’s intelligence, one notch down, yours to run.”

Swarm coordination moves into the weights. K3 Swarm Max coordinates an orchestrator and up to roughly 300 sub-agents across some 4,000 steps. The capability first shipped with K2.6 in April. What matters is where it now lives. Not in a harness bolted around the model but trained into the model itself. The Claude Code leak laid the stakes bare. The harness includes routing, memory, delegation, and policy. This is where a thousand companies have pitched their moats, but it is now much more vulnerable.

The million-token agent becomes real. Long context has been advertised for over a year and trusted by almost no one who runs agents in production. That’s because of a phenomenon known as “context entropy.” This describes the degradation that caps most production agents at ten steps or fewer. It worsens with window size rather than improving. K3’s BrowseComp result, beating both frontier models at the full million-token window without compaction, is the first independently run public evidence that the million-token agent is a working tool rather than a specification.

Now the counterweight. Fable 5 and GPT-5.6 Sol still win the overall index, the hardest software-engineering evaluations, and the evaluations closest to real economic work. A 51% hallucination rate is disqualifying for large classes of enterprise deployment. The closed frontier has not yet fallen.

Clearly, with the Kimi K3 release, the capability premium has retreated to the top two models. Everything below that tier, Opus-class capability included, now competes with an imminently self-hostable peer at task-cost parity.

The Geography Flipped: From Llama to Kimi, Qwen, and GLM in Eighteen Months

K3 did not arrive alone. It arrived as the crest of a wave: DeepSeek R1 in January 2025; Kimi K2, the first trillion-parameter open release, in July 2025; K2 Thinking in November; the Qwen line; GLM-5.2 in June, MIT-licensed at roughly a sixth of Western frontier pricing; MiniMax M3 at a twentieth; DeepSeek V4.

There is an important point to consider in this string of releases. All year, open-weight “parity” was vendor-reported, and all year the claims took a documented seventeen-to-twenty-one-point haircut when re-run on standardized independent harnesses. GLM-5.2 came closest. When Zhipu shipped it in June, I called it the first open model to break into the closed frontier cluster. It scored 51 on the same index where K3 now scores 57. Yet I still counseled caution, because Epoch’s independent evaluation was pending and open models flatter public benchmarks. K3 is the first release to clear the independent bar outright, at a higher tier, on the strictest harness available. Qwen 3.8-Max, three days later, is a reassertion of the pattern: a 2.4-trillion-parameter frontier claim with no independent run behind it yet.

The lineage carries a family trait. GLM-5.2 was the least token-efficient open model in its class, spending 43,000 tokens where MiniMax spent 24,000, effectively buying its capability with verbosity. K3 inherits the habit, but one tier higher. The open-weight wave keeps reaching the frontier by outspending it on tokens, which is exactly why the efficiency frontier, not the capability frontier, is where the next battle sits.

Meta, which carried the US open-weight banner for three years, stepped back from the Llama line this spring. Now its Superintelligence Labs flagship model is proprietary. The largest American platforms no longer field an open-weight strategy at all.

That has left a vacuum that Thinking Machines is hoping to fill.

Co-founded by Mira Murati, former CTO of OpenAI, the startup last week released Inkling. It represents a very different bet from anything Silicon Valley ever shipped: 975 billion parameters, Apache 2.0, paired with the startup’s Tinker fine-tuning platform, and positioned explicitly as not the strongest model available, but rather the best foundation for building your own.

Consider what Murati is wagering. She is betting against one-size-fits-all intelligence. Instead, she is wagering that the layer where durable value accumulates will be built around customization, context, and orchestration. The executive who helped build the closed system is now building the exit ramp.

The market is pricing the bet, not the benchmark. Thinking Machines raised $2 billion at a $12 billion pre-product valuation, with reported talks at $50-60 billion for a model sixteen points off the frontier. Inkling debuts at 41 on the same independent index where K3 scores 57. That means the best American open model is sixteen points behind the Chinese open frontier it answers. Its mixture-of-experts design, by Thinking Machines’ own account, largely follows DeepSeek-V3’s recipe, and its post-training was bootstrapped on synthetic data generated by Kimi K2.5. So, the American open-weight standard-bearer is built on Chinese architecture and finished on Chinese data, a dependency Thinking Machines says its next generation will shed.

Where Inkling does lead is revealing: 25,000 output tokens per task against GLM-5.2’s 43,000 and K2.6’s 38,000.

Put the pieces together, and the map has redrawn itself. In eighteen months, open source’s center of gravity moved from Menlo Park to Beijing and Hangzhou, and the American response is now carried by startups and sovereignty vendors, not platforms.

The Reversal: Why Kimi K3’s Open Weights Re-Centralize the Datacenter

At first glance, K3 appears to threaten the largest capital commitments in economic history. On closer inspection, it does something more interesting.

If Moonshot’s scaling-efficiency claim holds, frontier-adjacent capability is becoming cheaper to train per unit of intelligence. That does not invalidate the trillion-dollar capex thesis, but it does introduce a discount factor into its simplest assumption: that more compute is the only route to more capability. One datapoint does not overturn a scaling law. Call it a crack in the premise, not a break.

Now ask the more important question: where does a model like this actually run?

The open-weight wave was supposed to push inference toward the edge: smaller, distilled models running on laptops and phones, intelligence dissolving into devices. K3 reverses that vector. A 2.8-trillion-parameter mixture-of-experts model whose weights alone occupy roughly 1.4 terabytes, even under four-bit quantization, is not an edge model. It runs on datacenter accelerators with enormous memory requirements, regardless of who hosts it or where.

To “self-host” a K3-class model is therefore to buy or rent substantial accelerator and HBM capacity—inside a neocloud, a sovereign cloud, or an enterprise facility, but inside a datacenter all the same. Frontier-adjacent open weights do not disperse inference to the edge. They re-centralize it inside the data center.

The net effect on compute demand, I suspect, is therefore positive, but compositionally different. Demand migrates away from closed-lab training Capex and toward distributed inference hosting. It is also unusually memory-intensive demand: expert weights and context caches, multiplied across large numbers of concurrent agents, create a memory problem as much as a FLOPs problem.

Jevons does the rest. At no point in this discontinuity has cheaper capability per token produced fewer tokens.

When Cerebras filed to go public, I argued that the Inference Economy—an economy in which inference, rather than training, becomes the center of gravity—was the layer against which AI infrastructure should be valued. K3 delivers a demand shock directly into that layer.

And then there is memory. The reflex trade is easy to imagine. Kimi Delta Attention reduces the KV cache by roughly fourfold relative to standard attention, according to Moonshot. A smaller cache appears to mean less HBM per deployment, which in turn appears bearish for memory manufacturers.

That interpretation gets the causality backward. Cache efficiency is not a demand destroyer. It is a demand detonator.

The binding constraint on agentic AI has not been intelligence itself. It has been the cost of sustaining intelligence across long-context tasks. Million-token agents have existed on specification sheets for more than a year, but few organizations have run them in production because the cache economics made them prohibitive.

Kimi Delta Attention relaxes that constraint. And that relaxation is precisely what makes K3’s headline results possible: the BrowseComp run across the full million-token context window, and the 300-sub-agent swarm operating across 4,000 steps.

Cheaper long-context tokens do not mean fewer tokens. They mean elastically more of them. HBM freed at the level of the individual agent is redeployed into larger batches, longer contexts, and more concurrent agents—not smaller infrastructure bills.

This is the DeepSeek lesson replayed almost note for note. The efficiency panic of January 2025 was followed not by collapsing compute demand, but by record demand. The analysts who treated efficiency as a substitute for infrastructure spent the rest of the year discovering that it was an accelerant.

Read more

00:00 - Intro

00:01 - Podcast Insights and Market Developments: CoreWeave and Anysphere

04:38 - CoreWeave: Strategic Positioning and Anthropic’s Impact

08:59 - Enterprise AI Cost and Impact

12:03 - The Shift to Sovereign AI

14:37 - Agentic Memory and Emerging Tech Opportunities

20:47 - Emerging Frontiers of Memory

Chapter 11 · All chapters

This is the latest excerpt from AGNT: The Orchestration Economics Manifesto - An Investment Framework for the Agentic Era. Each Thursday, I explore a major theme of the Manifesto and unpack the frameworks, adding extra context with more recent developments. Note: The figures and sequential references are taken directly from the larger Manifesto.

Subscribe now

Read more

TLDR: SpaceX claims a $22.7 trillion opportunity in enterprise applications, but the post-IPO analyst models overwhelmingly underwrite compute rental rather than software, customers or switching costs. Cursor, Sand, and Grok now give SpaceX a credible mechanism to pursue that market: the coding-to-orchestration playbook that Anthropic used to enter the enterprise. But SpaceX is beginning after Claude, OpenAI, and Microsoft have already occupied the field, with no shipped general-purpose agent or demonstrated external adoption. The enterprise thesis has therefore moved from unsupported to plausible, but remains a time-sensitive option. SpaceX’s valuation ($1.8T as of July 14^th) prices that option as though the playbook had already been executed.

Subscribe now

Last week, the SpaceX valuation debate was compressed into five days. On Tuesday, July 7, the quiet period (the 25-day post-IPO window during which underwriters cannot publish research) lifted, and the lips of more than a dozen brokers were finally unsealed as they publicly initiated coverage, all but one at a buy-equivalent rating (the lone Neutral carries a $131 target). On the same day, Anthropic extended Claude Cowork, its general work agent, to mobile and web.

On Wednesday, SpaceX’s AI division released Grok 4.5, its bid for the model frontier. A day later, OpenAI unveiled ChatGPT Work, an enterprise agent powered by GPT-5.6. Then, that same afternoon, The Information reported that Cursor - the coding company SpaceX is acquiring for $60 billion - was developing a general-purpose work agent codenamed Sand and had begun testing it internally in late June. It remains unnamed, unpriced, and unlaunched. One week: the research, the model, the rivals’ agents, and the leak of SpaceX’s own, while the stock traded below its first-day close. If you want to judge the largest TAM number ever printed in a prospectus, the evidence is now on the table. Or should be.

Instead, that number remains the $800 billion black hole I wrote about before the IPO and now approaches $900 billion at the company’s current price.

The force creating that black hole was the S-1’s $22.7 trillion “enterprise applications” claim: 86% of the AI opportunity, supported by one sentence and no visible bridge from SpaceX’s actual compute, data, and model assets to enterprise workflows, customers or switching costs. Except for references to the “Macrohard” product whose work has stalled at xAI per the same The Information article.

One month later, that conclusion deserves refinement, but not reversal. The Cursor acquisition, the emergence of its general-purpose agent Sand, Grok 4.5, and SpaceX’s vertically integrated compute stack now supply a credible valuation mechanism. The black hole is no longer entirely empty. It has become an option.

Yet the banks that initiated coverage have not underwritten that option as an applications business. They have mostly underwritten capacity, while allowing the applications narrative to carry the multiple, while effectively dodging this issue.

One can now see SpaceX/xAI assembling parts of the mechanism that Anthropic already demonstrated with resounding success: enter the enterprise through coding (the “Coding Wedge”), where output can be verified; expand into general work; then occupy the orchestration layer where a company’s context and workflows compound around the agent. SpaceX now has real ingredients for a version of that playbook and a cost structure Anthropic does not.

What it does not have is Anthropic’s head start, a shipped general-purpose enterprise agent, external adoption or an uncontested field in frontier capabilities. Nor would winning the orchestration layer make the filing’s $22.7 trillion revenue pool real at face value. The same automation that expands the addressable work also lowers its price as I develop it later.

The Enterprise Applications business of SpaceX has moved from an unsupported assertion to a credible but time-limited option, while the valuation prices the playbook as though it had already been run. In this article, I want to explore what Wall Street actually modeled, whether SpaceX can execute the Anthropic path, and what remains when the option is separated from the infrastructure business.

Share

The banks priced the small bucket and sold the large one

The ratings tell one story: all but one initiation at a buy-equivalent, with targets running from $131 at the lone Neutral to $800 (!) at the most exuberant. The models beneath them tell another, and it is the same story at every bank that published one.

Across the initiations, the projected AI revenue is overwhelmingly compute monetization - capacity built and sold or rented to third parties. Enterprise software and agents, the business that is supposed to justify the $22.7 trillion, survive as a residual: on the order of a tenth of the modeled AI revenue, standing in for 86% of the stated opportunity in the S-1, inside segments projected at the margins of a data-center landlord rather than a software empire.

The tell is not the estimates. It is the unit of account. The street’s frameworks for SpaceX’s AI segment are built in dollars of revenue per gigawatt of capacity: anchor the addressable market to global cloud infrastructure spending - a figure more than an order of magnitude smaller than management’s $22.7 trillion - sort every use of a gigawatt into workload categories, and apply a blended capacity yield, on the logic that SpaceX will steer its compute toward whichever use pays best in a given quarter. In that arithmetic, an enterprise application is not a business with customers, seats, and switching costs. It is a higher-yielding use of a gigawatt - a premium tenant for the same capacity.

Nobody has ever valued Salesforce in dollars per gigawatt. The choice of denominator tells us everything: what the street can underwrite is capacity, flexed toward whichever meter runs hottest. What it cannot underwrite - what no initiation even attempts - is an applications franchise.

The frameworks are candid about one more thing. Today’s hosting economics reflect scarcity, not steady state: the flagship compute deals are structured, by Musk’s own public description, with mutual cancellation on 90 days’ notice, at rates the street broadly expects to normalize lower as supply arrives.

In every credible model, then, the revenue comes from the small bucket: infrastructure, 9% of the company's stated opportunity by its own arithmetic. The narrative and the multiple come from the large one. A dozen reports in one week, and not one names the seam.

So, the question the sell side declined to answer falls to us: is there a credible path from a compute business to the $22.7 trillion? There is. We know it because someone has already walked it.

Read more

Chapter 10 · All chapters

This is the latest excerpt from AGNT: The Orchestration Economics Manifesto - An Investment Framework for the Agentic Era. Each Thursday, I explore a major theme of the Manifesto and unpack the frameworks, adding extra context with more recent developments. Note: The figures and sequential references are taken directly from the larger Manifesto.

Subscribe now

Read more

TLDR: On July 1, CEO Alex Karp went on CNBC to discuss Palantir’s expanded Nvidia partnership and delivered a nineteen-minute broadside against OpenAI and Anthropic: enterprises are “livid” because they are paying for “tokens that create no value” while the labs harvest their data and alpha. Karp is right that enterprises are frustrated with exploding token costs and frontier labs capturing too much value/control. But he is wrong that Palantir’s platform (Ontology + Nemotron) is the necessary cure that makes agents “safe, useful, and precise”. Those properties come from the specification and verification core, which Palantir has a strong version of, but does not own. Open weights are not the frontier. The labs are already moving inside customer perimeters. Therefore, Palantir is half right on the diagnosis but overclaims on the prescription.

Subscribe now

Read more

Chapter 9 · All chapters

This is the latest excerpt from AGNT: The Orchestration Economics Manifesto - An Investment Framework for the Agentic Era. Each Thursday, I explore a major theme of the Manifesto and unpack the frameworks, adding extra context with more recent developments. Note: The figures and sequential references are taken directly from the larger Manifesto.

Subscribe now

Read more

TLDR: French insurtech Alan raised €480 million in a round that the Financial Times first called one of the largest by a “non-AI” company. That mislabeling of Alan points to a more fundamental error: how markets keep misjudging which companies are making the transition to the Agentic Era. In the Orchestration Economics framework, Alan serves as a case study of a company making the crossing. Alan is a disruptor that owns its context, workflow, and the verifier that decides whether its agents are right. That last asset is the most decisive and least-watched test of who crosses the agentic threshold and who is displaced. In Alan's case, the binding constraint may ultimately come from capital rather than technology.

Subscribe now

When the Financial Times described French insurtech Alan’s latest funding round as Europe’s biggest “non-AI” fundraising of the year, it mislabeled the company in an interesting way. In this case, the miscategorization of the unicorn is not just about marketing buzzwords.

On June 25, the paper broke a story that offered a counter-narrative to a venture world that seemed interested in nothing but AI: “Prosus leads €480 million investment in French health tech startup Alan,” read the headline over a subhead noting that the “Paris-based group raises one of Europe’s largest non-AI start-up rounds this year.” The FT later swapped that subhead for the more anodyne “The deal values the 10-year-old Paris-based group at €5.5bn.”

The difference between the two subheads is worth examining. But not just to question the FT’s editorial judgment.

Rather, the miscategorization is entirely understandable because it is a microcosm of the larger struggle playing out across markets as they try to price the impact of generative and agentic AI on legacy software. This is most evident in the binary debate of software versus AI. The market’s reflex may be directionally correct for some categories, but it is analytically lazy. Alan is an example of why the binary framing is wrong. It is proof that some existing companies can make the crossing to the Agentic Era.

As I wrote in Orchestration Economics when discussing the February 2026 SaaSpocalypse, this is “a confused, simplistic attempt to price a structural shift in where control, coordination, and value capture reside”. This is not the death of SaaS. It is the Software Sorting,” a re-ranking of where value will sit “when autonomous agents become the primary actors inside enterprises.”

The harder question for investors is how to tell which companies can make the crossing and which can’t. That question reaches well beyond software.

In Orchestration Economics, I reserve a specific label for a company that has secured the structural position to capture value in this new paradigm: AGNT. It is an end state, not a badge handed out for momentum. A company earns it only once it holds the orchestration position and shows the value separation that proves it.

Alan has not arrived there. But of the companies I track, it is one of the clearest emerging orchestrators: a disruptor already building the new playbook rather than an incumbent wondering whether it can.

Share

Electricity, Computers, and the ‘Non-AI’ Reflex

The “non-AI” reflex is not new. It is the latest version of a mistake that markets make at the start of every general-purpose technology: confusing a force that reorganizes an economy with a like-for-like upgrade.

When electricity reached the factory, the first generation of owners treated it as a cleaner alternative to steam engines. They pulled out the central steam plant, dropped a single large electric motor in its place, and kept the same overhead shafts and belts driving the same machines in the same order. The power source changed. The factory did not. And for three decades, the promised productivity gains barely showed up in the numbers. They arrived only when a later generation stopped swapping the engine and rebuilt the factory around the new principle: small motors on each machine and floor plans laid out around the flow of work rather than the geometry of the belts. Productivity then climbed steeply, and industrial leadership reshuffled.

The economic historian Paul David used this story precisely to explain why the computer, too, took decades to surface in the productivity statistics.

“Non-AI” is the modern “just a cleaner engine.” It looks at Alan, sees an insurer selling insurance, and files it under the old economy.

Alan’s First Wave: From €173 Million in 2024 to €804 Million ARR

Go back to September 2024, barely two years ago, in a timeline that already feels like another epoch. It was less than two years after the first public release of ChatGPT. Anthropic would not publish the Model Context Protocol for another month. Generative AI dominated the conversation, with the turn toward agents still over the horizon.

That month, Alan, already a unicorn, raised €173 million at a €4 billion valuation. It was the largest insurtech round in Europe that year, accounting for close to one in four euros invested in the sector. The mood elsewhere was unambiguous: Insurtech was a dead category, software multiples were stumbling, and the only heat in the room was generative AI.

But even then, Alan had established itself as a disruptor. It received the first new health-insurance license granted in France since 1986 and, in the decade since, has grown from nothing to 1.1 million members and roughly 37,000 corporate clients across France, Belgium, and Spain.

I argued at the time that the valuation was not, in fact, crazy. Alan’s leadership had already begun an aggressive investment in generative AI. Not a chatbot bolted onto a legacy stack to pass as cutting-edge, but AI worked into the core. “In Alan’s case,” I wrote then, “GenAI is already enabling gross margin improvement that has solidified its unit economics, put it on a path to profitability, and given it an advantage over other insurance incumbents.”

The detail mattered: Alan had integrated AI across the business, reporting a 28% cut in per-member administrative cost in 2023, with automation concentrated where insurers bleed: claims analysis and fraud. My case was that recurring revenue was the wrong lens for Alan, because it competes against incumbent insurers rather than software peers, and that the real story was margin. Gross margins are razor-thin in insurance, which is what sank so many insurtechs. It helped that Alan’s founders are also Mistral co-founders, which gives the company privileged access to sovereign European models in a domain where data residency is not optional.

That was early. The company used the round to accelerate, and it had already placed itself at the vanguard of the agentic crossing, in the part of the economy I describe as Wave One in Orchestration Economics: insurance, with claims adjudication against codified coverage rules, deep historical loss data, and a high routine-to-judgment ratio, alongside banking, corporate services, and customer support, where autonomous resolution has already been demonstrated at scale within weeks of deployment.

That performance is reflected in the numbers. ARR reached €804 million in early 2026, up from €340 million two years before, growth of 48% and then 53% in consecutive years. Management is guiding past €1 billion this year. Meanwhile, its valuation has climbed from €2.7 billion in 2022 to €5.5 billion today. Unusually for a company growing this fast, it is also moving toward profit: France turned EBITDA-positive in 2025, and group losses roughly halved.

That combination is the analytically interesting part. High-growth challengers usually buy growth at a loss. Profitable insurers usually do not grow at this rate. Alan is doing both, and its own accounts credit AI for the margin side thanks to automation concentrated in claims and fraud, where insurers tend to bleed.

Alan is already a challenger, restructuring around AI. It is not acting like an incumbent debating whether to embrace AI or simply defending its existing position.

Read more

Chapter 8 · All chapters

This is the latest excerpt from AGNT: The Orchestration Economics Manifesto - An Investment Framework for the Agentic Era. Each Thursday, I explore a major theme of the Manifesto and unpack the frameworks, adding extra context with more recent developments. Note: The figures and sequential references are taken directly from the larger Manifesto.

Subscribe now

Let’s return to the insurance workflow. The master agent receives a goal: evaluate this risk and produce a quote that fits our growth and risk constraints. The extraction agent receives a task: pull the relevant data from this document. The fraud detection agent receives a task: check this submission for anomalies. The pricing agent receives a task: calculate the payout given these parameters.

All four are agents. All four orchestrate tools. All four sit in the Orchestration Layer. But the master agent controls routing. It decides which specialists to invoke, in what order, and under what constraints. It defines the workflow. It validates the outputs. It determines when the goal is achieved. The specialist agents execute tasks defined by someone else. They may be brilliant within their domains. But they do not see the whole map. They do not decide whether the claim gets processed. They do not own the relationship with the human who submitted it.

Chapter 7 established that this hierarchy creates disproportionate value capture. The First Law explains why: it is not coordination alone that creates the advantage. It is in proximity to the human’s original intent. The master agent sits closest to the moment a human expresses a goal. The pricing agent sits furthest from it, several translations downstream. That distance determines everything: defensibility, pricing power, switching costs, and bypass risk.

The principle generalizes across the entire agentic economy. There is a hierarchy of positions relative to intent, and your location determines the durability of your orchestration position:

Intent Origin carries the highest value. This is where goals are first expressed in natural language, unstructured, with high ambiguity. The human who submits “evaluate this risk” is expressing intent at the origin. In enterprise software more broadly, search interfaces occupy this layer: conversational interfaces, ambient assistants, operating systems, enterprise collaboration tools, and autonomous workflows. Whoever controls the intent origin potentially controls routing.

Intent Capture carries strong value. This is where goals become structured as they are translated into specific actions, mapped to known workflows, and scoped with constraints. When the master agent decomposes “evaluate this risk” into discrete tasks for each specialist, it is performing intent capture. If agents intercept intent at the origin layer and route it directly to execution, the capture layer is skipped entirely.

Intent Processing carries moderate value. This is where goals are executed. Data is read and written, APIs are called, and workflows run. The extraction agent and the fraud detection agent occupy this layer. Essential work. Nothing happens without it. But it does not control where intent originates or how it gets structured.

Intent Output carries the lowest value. This is where results are viewed as dashboards refresh, reports are generated, and notifications are displayed. This layer is one abstraction from replacement. When the master agent synthesizes results and delivers the outcome directly to the human who expressed the goal, separate output displays become redundant.

The further upstream you sit, the more durable your moat. The further downstream, the more replaceable you become. Because the Orchestration Layer above you can substitute you without the user noticing. The insurance company does not care which extraction agent runs. It cares that the master agent delivered the right quote.

Share

Why Upstream Wins

The hierarchy is not merely a ranking. It reflects a structural asymmetry in how value flows through agentic systems. The entity at the intent origin has three advantages that entities downstream do not:

Routing authority. The intent origin decides which downstream systems get invoked. Every goal expressed is an opportunity to engage your capabilities, route to your ecosystem, and monetize through your platform. This is the economic engine that made AWS successful: control the compute layer, and you can upsell storage, databases, machine learning services, and a thousand other capabilities. Intent capture is the agentic equivalent. Control the orchestration surface, and every user goal becomes a distribution channel.

Relationship ownership. The human interacts with the intent surface. The human trusts the intent surface. The human returns to the intent surface. Everything downstream is invisible to the user. It is mediated, abstracted, and replaceable. The intent surface owns the relationship. Everyone else is a vendor.

Phase transition capture. Connect this to the economics of Chapter 7. The phase transition to Orchestration Economics only accrues to the entity that delivers the complete outcome. That entity must sit at or near the intent origin, because only the intent origin can promise the customer that if they receive the goal, it will deliver the result. An orchestrator at the processing layer can coordinate agents effectively, but it cannot deliver the autonomous function the customer is paying for. It depends on someone upstream to provide the goal. Someone upstream can bypass it. An orchestrator at intent origin owns the goal itself, and everything downstream flows from that ownership.

Not all data enables these advantages equally. Customer behavioral data, such as how users interact, what they choose, and what patterns they follow, creates the strongest orchestration advantage because it feeds directly into routing decisions. Operational transaction data creates the strongest execution advantage but does not grant routing authority. The implication for investors is direct: companies that accumulate behavioral data at the intent surface compound their routing advantage with every interaction. Companies that accumulate transactional data downstream build strong specialist positions but remain vulnerable to bypass. The corollary is severe for companies positioned downstream. If you are a point solution, such as a specialized sales engagement tool, and the user’s goal is expressed in Slack and orchestrated by Agentforce, you are competing to be the sub-agent that gets invoked. Your switching costs collapsed. Your direct relationship with the user eroded. You moved from captain to crew. The crew is replaceable.

The Software Inversion

For two decades, enterprise software moats were constructed downstream. You won by owning the system of record. This is the database where critical business data lives, surrounded by workflows that made switching painful. Salesforce built an empire on this principle. So did Workday, ServiceNow, and SAP.

The Orchestration Layer inverts this. When an agent mediates the interaction, the system of record becomes just another API call. The agent does not care whether your CRM is Salesforce or HubSpot. What matters is whether the agent can access the right context and orchestrate the sequence of actions needed to fulfill the user’s goal. Moats no longer form where data sits. They form where intent originates.

Salesforce recognized this before most of the market. Its repositioning of Slack at Dreamforce 2025 is the First Law made concrete. Restricting AI companies’ access to Slack data looked defensive. The sequence that followed instead demonstrated an offensive strategy by governing access through MCP, the Agentforce runtime, and first-party agents embedded directly in Slack.

Salesforce moved the moat upstream, from owning the database where records sit to owning the surface where goals are expressed. Slack became the system of intent. Customer 360 remained the system of record. Agentforce became the Orchestration Layer, binding them. The company understood that controlling the origin of intent is more valuable than controlling any system downstream.

This continued in April at Salesforce’s TDX developer conference in San Francisco. Salesforce's strategy unveiled at TDX 2026 provides a concrete illustration of the First Law in practice.

Rather than defending Customer 360 as the primary destination for work, Salesforce deliberately moved its competitive position upstream, toward the point where work begins. Headless 360 exposes the underlying platform as APIs, MCP tools, and agentic services, making the traditional application interface increasingly optional. At the same time, Slack is repositioned as the system of intent, Agentforce as the orchestration layer, and Data 360 as the context substrate that informs routing decisions.

This architecture reflects an important strategic realization: the long-term moat no longer resides in owning the system of record where data is stored, but in owning the surface where users express goals and where agents accumulate the behavioral context needed to orchestrate future work. The CRM becomes execution infrastructure; the intent surface becomes the source of durable economic power.

The same principle operates at every scale. Within OpenAI’s GPT-5, a built-in router analyzes user intent and directs processing to the appropriate internal model variant. The router sits at the intent origin inside the model. Platforms like Slack or Teams must do the same thing across entire ecosystems. The architecture is fractal: whoever captures intent first controls what happens next, whether “next” means selecting a model variant or orchestrating a fleet of enterprise agents.

The Protocol Test

Protocols provide the sharpest test of the First Law.

Chapter 7 established bypass risk as the counterforce to orchestration advantage. MCP and A2A, along with their rapid adoption by every major platform, standardize how agents connect to systems and to each other. That standardization dissolves integration friction, the difficulty of connecting systems that once protected many orchestration positions. The First Law predicts exactly which positions survive this dissolution and which do not.

Protocols can standardize every layer below the intent origin. They can make tools interchangeable, specialist agents substitutable, and integrations frictionless. If every CRM exposes the same agent endpoints via MCP, an orchestrator has little structural reason to prefer one over another. Switching costs collapse. Differentiation shifts toward price. Margin compresses. This is the crew’s fate in a world of universal protocols. But protocols cannot standardize the moment a human expresses a goal. They cannot standardize the trust relationship between a user and the surface where they articulate what they want. Intent origin is protocol-resistant because it depends on human habit, institutional workflow, and accumulated context. None of these can be specified in an API schema.

Protocols commoditize execution. Intent surfaces capture value.

The orchestrator that relied on integration friction has no moat left. The orchestrator at intent origin has a moat that protocols reinforce because every new protocol-compliant tool that connects to its ecosystem makes the intent surface more valuable, not less. More tools mean more capabilities the captain can route to. The crew gets more substitutable. The captain gets more powerful.

Strategic Positioning

The First Law creates a simple diagnostic for any company in our investment universe: where do you sit in the intent hierarchy, and can you move upstream?

For the systems of record, the processing engines, the output layers, the imperative is to move from downstream to upstream. Build the agent cockpit, not just the system of record. If moving upstream is not feasible, differentiate so aggressively that you become irreplaceable to orchestrators. Be the specialist so good that the captain cannot sail without you. Workflow lock-in will not protect you. Data gravity will not protect you. The question is whether you can become the agent that other agents depend on.

For horizontal orchestrators competing to be the default intent surface, the imperative is speed. Race to become the place where users start their day and express goals. This probably means conversational interfaces rather than traditional application UIs. Invest in context accumulation and memory architectures because the depth of your conversational memory prevents a bypass when the next intent surfaces.

For specialized agents at the execution layer, embrace protocols and compete on quality, speed, and cost. Be the best sub-agent in your category, and you will be routed millions of times. Fail to be best in class, and you will be replaced overnight. You are the crew. Make yourself indispensable crew.

Where does value concentrate five years from now? Three scenarios frame the range:

Fragmented orchestration: every application embeds its own agent layer. Slack has Agentforce. Microsoft has Copilot. Intent capture is distributed, and moats remain traditional.

Consolidated orchestrators: a handful of platforms emerge as dominant intent gateways, orchestrating best-of-breed sub-agents behind the scenes. Downstream tools become commoditized utilities.

Decentralized agent mesh: open protocols enable any agent to invoke any other agent, and value flows dynamically based on performance rather than ownership.

History suggests a hybrid: consolidation around dominant orchestrators, plus a long tail of specialized agents accessible via protocols. But in all three scenarios, proximity to user intent is the strategic high ground. The players who control where goals are expressed will have structural advantages in routing, context access, and monetization. The players who do not will compete on price.

If you neither own intent nor provide differentiated capabilities to the orchestrator, you risk becoming a replaceable API call in someone else’s plan.

The First Law

The First Law establishes the first condition for defensible orchestration: proximity to intent determines where value concentrates, who controls routing, and whose position survives protocol standardization. Moats form where intent originates, not where data sits. The captain who hears the human’s goal first captures the economics of the phase transition. Everyone downstream competes on execution.

Owning intent is necessary, not sufficient. Return to the insurance example one more time. The master agent sits at the intent origin. It controls routing. It captures the phase transition economics. But what happens when a competitor builds a rival master agent for the same workflow? Both sit at the origin. Both offer orchestration. What determines which one the customer stays with?

The answer is not who arrived first. It is who built the deeper context. Who accumulated the operational intelligence that makes orchestration effective in ways a new entrant cannot replicate on day one?

That is the Second Law.

The views and opinions expressed in this publication are those of the author alone and are based on publicly available information. The expressed views and opinions do not constitute investment advice, a solicitation, or a recommendation to buy or sell any security or financial instrument. The author may hold positions in the securities of companies mentioned. Certain companies referenced may be current or former clients of, or counterparties to, the author or affiliated entities; such relationships will be disclosed where applicable. Past performance is not indicative of future results. To the fullest extent permitted by applicable law, the author does not accept any liability for any loss or damage arising from reliance on this content. Readers should conduct their own independent due diligence and consult a qualified financial advisor before making any investment decision.