Every board asks the wrong question: how confident are you?

Confidence is a terrible investment criterion. History is full of executives who were catastrophically wrong with total conviction. Confidence isn’t insight. It’s charisma, or a good run, or enough distance from the downside that you stop feeling it.

The question that actually separates enduring companies from transient ones is different.

What must be true, regardless of which future arrives?

Leaders who consistently arrive early aren’t better forecasters. They’re better students of what the present can no longer sustain.

The Bankruptcy of Point-Forecasting

Corporate strategy is addicted to prediction. Five-year models. TAM slides. Roadmaps. Projected IRR. All useful, most of the time. At the exact moments that matter, all of it fails.

Forecasts fail because they extend yesterday’s line into a future that doesn’t move in lines. Roadmaps fail because what you ship looks nothing like what you pitched. TAM estimates fail because you can’t size a market that doesn’t exist yet with data from the market that did.

Rejecting the forecast doesn’t mean rejecting prediction. It means moving the bet from the product to the economics underneath it.

The trap is mistaking a constraint that’s about to be engineered away for one that can’t be.

Skeptics will say this is post-hoc rationalization — that invariants only look obvious in the rearview mirror, and every failed bet once called itself a permanent law too. Fair challenge. So here’s a test you can run before the market resolves it, not after.

The Veto Test

Every durable constraint survives because something outside the technology itself keeps it alive — physics, institutions, or coordination. The three questions below are just a way to find that force before the market prices it in.

Ask them of any constraint you’re tempted to call permanent.

How many independent parties would have to move together to dissolve it? One — a single engineering team ships a better algorithm — and assume it’s temporary. Several, none of whom report to each other — a regulator, an insurer, a court, a standards body all have to align — and you’re looking at something with real durability, at least on a multi-year clock.

Does anyone with power over the constraint actually benefit from keeping it? Bandwidth scarcity had no defender. Carriers wanted more usage, not less; nothing with leverage over the constraint was rooting for it to survive, so once the engineering existed, it collapsed fast. Contrast that with liability. Insurers, plaintiffs’ bars, and licensing boards all have a business model that depends on accountability staying somewhere identifiable. A constraint with an entrenched defender has inertia a pure engineering gap never does.

Is the fix an improvement in the technology that’s becoming abundant, or does dissolving the constraint require a resource that sits off that improvement curve entirely? Things on the curve get cheaper on schedule. Physical infrastructure and institutional coordination usually sit off it.

Run bandwidth through this and it fails all three: one veto-holder, no defender, pure engineering fix. Run data sovereignty through it around 2010 and it’s closer — several parties, real friction, but still no defender fighting to keep data landlocked once the engineering existed elsewhere. It was never going to hold forever; the test tells you how much scrutiny a claim deserves before you commit capital.

Real conviction doesn’t come from guessing which limitation feels permanent today. It comes from finding what’s still standing after engineers have had a decade to attack it.

Containerization makes the same point from the other side, and it’s worth running the test forward. Ship size has one veto-holder — whichever yard builds the next hull — no entrenched defender, and it sits on shipbuilding’s own improvement curve: a false invariant, visible as one before the fact. Ports, rail, and customs scheduling have several veto-holders who don’t report to each other, an entrenched defender in every port authority protecting its place in the trade lanes, and infrastructure that sits off that curve entirely. Run the test in 1965 and it points at the chokepoint, not the hull, years before the outcome was obvious.

The Law of Migrating Scarcity

Markets don’t pay for abundance. They pay for whatever abundance can’t eliminate. Technology only destroys the constraints that sit on its own improvement curve — everything that endures sits somewhere else. Migrating Scarcity tells you where value goes next. The veto test is just the instrument that tells you whether the scarcity you’re eyeing is actually durable enough to bet on.

The claim is narrower than “value migrates to scarcity.” Durable bets are the ones where the surviving scarcity can’t be eliminated by improvements in the technology that’s becoming abundant. Sometimes that surviving scarcity is institutional — liability, licensing, permission. Sometimes it’s physical — a port, a fab, a grid. Both are outside the reach of the thing getting cheaper.

AWS wasn’t a bet on hosting. It was a bet that software velocity would stay bottlenecked on physical server provisioning regardless of what got built on top — land, power, permitting, capital, none of which gets easier just because code does. The constraint sat off the curve, so the value moved there. NVIDIA’s early push into CUDA wasn’t a bet on deep learning. It was a bet that an expanding class of computational problems would keep outgrowing sequential architectures, regardless of which application eventually created the demand — a hardware limit no amount of better software was going to route around. Same question, both times: once this gets cheap, what still sits off the curve? AI is the live version of that question.

Run AI through that filter and be honest with yourself. Raw intelligence is collapsing in cost. So are generic guardrails and compliance copilots — commoditizing on the same schedule as the models. None of that is the invariant. Novelty is often mistaken for durability.

What doesn’t collapse is who’s on the hook when an autonomous system gets a regulated decision wrong — credit, clinical triage, capital allocation. Nobody sues the model; the regulator and the court go after whoever was running the process.

Software can produce a verifiable, immutable log of what happened. It cannot absorb the consequence of being wrong. That has to sit somewhere, with someone — and that’s where the value lands.

Run this through the same test rather than just asserting it. Veto-holders: regulators, insurers, courts, and licensing bodies all have to move together — several, not one. Defenders: insurers and licensing regimes profit from accountability staying identifiable. Fix type: legal reallocation, not a technology improvement. It clears all three, which is a different claim than “trust me, it feels permanent.”

This framework can fail. If regulation follows the path of Section 230, liability could dissipate rather than concentrate — and institutional accountability would be a far weaker moat than this essay argues. Watch legislatures and insurance filings, not court dockets: a blanket safe harbor shows up as a statute, a concentrating one shows up as a license.

Staging Capital Behind Inevitability

Identifying an invariant tells you where to bet. It doesn’t tell you when to size the bet.

Markets pay you for prediction only in hindsight. In real time, they price inevitability the moment it becomes obvious — and by the time it’s obvious to everyone, you’re paying retail for something you should have owned early.

But finding the right invariant doesn’t remove the timing problem. Being five years early looks identical to being wrong, at least on the P&L. Conviction tells you where the value lands. It doesn’t tell you when to deploy — and that needs an actual mechanism, not a hope.

Two signals, staged:

Deploy exploratory capital once a core cost — inference per complex workflow, say — crosses a threshold where mass deployment stops being a maybe and starts being arithmetic.

Deploy at scale only when clients start actually moving liability onto you in the contract. Real indemnification. Outcome-based pricing. Not a service-credit slap on the wrist for downtime. Watch who holds the leverage here — clients often demand indemnification before a vendor can actually price and carry it, and taking on liability you can’t afford is the same mistake as deploying too early.

Move before the second signal, and you’re funding the market’s growing pains on your own balance sheet. Wait past it, and you’re buying in at the price everyone else already figured out.

Strategy isn’t calling the future correctly. It’s being honest about which parts of today are already unsustainable, finding what survives the shakeout, and having the discipline to stage the bet instead of dumping it in all at once.

Boards keep asking the wrong question. Next time someone asks how confident you are, ask instead: what must still be true if every prediction on this slide turns out to be wrong? That’s where durable strategy begins.

Before you approve the next strategic investment, delete the forecast slide and ask one question instead: if this technology gets 100x cheaper, what constraint still controls the outcome?

The market doesn’t reward the people who guessed the future. It rewards the people who identified the constraints the future couldn’t escape.

When an enterprise giant falls, the post-mortem almost always blames a lack of vision.

We love the story of clueless executives ignoring the future. It’s comforting. If failure is just a lack of foresight, the fix is easy: hire better consultants, buy clearer forecasts, and hold better offsites.

Except it’s rarely true.

Blockbuster didn’t ignore streaming; they built a video-on-demand service with Enron in 2000, years before the infrastructure could support it. Kodak didn’t ignore digital photography; its engineers invented the digital camera in 1975, and management poured billions into digital imaging over two decades.

And in the 2010s, General Electric didn’t ignore software. Under Jeffrey Immelt, GE launched GE Digital and poured billions into its Predix platform, correctly sensing that heavy industrial assets would eventually require real-time telemetry and edge software.

Their strategies weren’t wrong. Their vision wasn’t late. Their clocks were.

The Law of Migrating Scarcity

We are living through a fundamental regime change in how value is created.

When technology makes a previously scarce resource abundant, economic value rapidly migrates to the next immediate bottleneck.

In the 1990s, computing hardware was scarce. Value accrued to silicon and box manufacturers.

In the 2000s, hardware became abundant; software and digital distribution became scarce.

Today, AI is making code generation, data synthesis, and strategic scenario analysis abundant.

For decades, strategy itself was scarce. Access to market data was scarce. Industry analysis was scarce. Strategic synthesis was scarce.

AI is rapidly making each of those cheaper. Whenever scarcity disappears, value moves. It has moved again.

The scarce resource is no longer knowing what to do.

It is the institutional capacity to rewire the organization faster than the technology clock compounds.

The Two Clocks

Every enterprise runs on two clocks ticking at fundamentally different speeds:

• The Technology Clock: The rate at which capabilities compound, models improve, and costs collapse. It moves exponentially.
• The Organizational Clock: The rate at which governance, budgets, incentives, and talent adapt. It moves linearly, and usually at a crawl.

The root of this friction is simple: Technology scales by copying code. Organizations scale by changing people.

You can deploy software instantly. You cannot instantly duplicate trust, rewrite sales compensation plans, or strip legacy fiefdoms of their budgets. Software compounds through silicon; institutions adapt through human consensus—one budget battle and committee meeting at a time.

Organizational Rewiring Latency

If competitive advantage is constrained by institutional adaptation, we need to name the variable that actually dictates survival.

Call it Organizational Rewiring Latency: the elapsed time between recognizing a strategic imperative and embedding the corresponding operating model as the institution’s unthinking, default behavior.

I believe Organizational Rewiring Latency is the missing variable between seeing the future and becoming it.

When GE Digital stumbled, it wasn’t because executive leadership lacked resolve or capital. They had both. It failed because while capital moved, the underlying organizational clock remained frozen.

Industrial salespeople were still incentivized on long-cycle hardware margins. Software capabilities were forced to route through legacy industrial equipment divisions. GE mistook capital allocation for organizational rewiring.

Executing aggressively toward a fundamentally flawed premise—like Quibi pouring billions into short-form media—is fatal. But moving with total strategic clarity while locked in high organizational latency is equally fatal.

The New Competitive Baseline

For decades, management theory obsessed over execution quality: process rigor, five-nines reliability, and pristine rollouts.

In compressed technology cycles, execution latency eats execution quality for breakfast.

If Enterprise A takes three years to launch a perfectly polished automated architecture, and Enterprise B takes six months to deploy an imperfect 80% solution in a reversible domain, Enterprise B is likely to win.

While Enterprise A spends thirty-six months perfecting its rollout in committee, Enterprise B builds real-world operational feedback loops, resets its cost structure, and trains its people to operate in the new reality. Enterprise B doesn’t just win the market; it systematically lowers its organizational latency for the next technology shock.

The organizations that dominate the next decade will not be those that recognize the future first.

They will be the ones that make it their default fastest.

When Products Become Politics

When Washington accused Beijing-based Moonshot AI of illicitly extracting intelligence from Anthropic’s flagship model to train its open-weights architecture, much of the commentary treated it like an operational detective story. The analysis fixated on technical mechanics: proxy networks, server routing, and API terms.

These specifics miss the underlying system at work.

Even if every allegation leveled by Washington is entirely accurate, the structural dynamic remains unchanged: When technology becomes impossible to monopolize economically, competition shifts beyond products into the institutions that govern markets.

Politics is one arena. Regulation, standards, procurement, certification, and national security are others.

Institutions become the dominant proprietary moat after technology becomes a commodity.

The Relocation of Scarcity

Markets do not eliminate scarcity. They relocate it.

Every major technology wave creates abundance somewhere in the value chain. Every wave also creates a new bottleneck somewhere else. The winners are rarely those who protect the old scarcity; they are the ones who recognize where the new one has formed.

In the early phase of any strategically important technology—where deployment depends on trust, safety, infrastructure, or national capability—value concentrates around raw engineering capability. Breakthroughs are scarce, proprietary, and expensive to discover. The firms that command early algorithmic or manufacturing advantages capture enormous economic rents.

Anthropic spent billions establishing the initial scarcity around frontier capability. Yet, when open-weight architectures achieve near-parity in a matter of weeks, they demonstrate how quickly raw engineering scarcity collapses in real time.

Eventually, the technology commoditizes. Efficient architectures emerge, open-weights models achieve near-parity, and specialized distillation techniques dramatically reduce the cost of approaching frontier capability.

As engineering scarcity disappears, institutional scarcity becomes the new bottleneck.

Permission is simply scarcity expressed through institutions.

In the Moonshot episode, the initial public countermove moved institutionally rather than commercially—emerging as a policy claim and regulatory warning routed through Washington rather than an immediate price cut or API overhaul.

Institutions are the mechanisms that allocate permission: governments, regulators, standards bodies, procurement processes, certification regimes, courts, and enterprise governance. Once products become abundant, access, certification, compliance, and legitimacy become the scarce resources that determine who captures value.

When raw technological capability becomes abundant, pricing power collapses and margin compression sets in. At that precise inflection point, firms can no longer defend margins through engineering alone. Competition migrates elsewhere—not to better products, but to the institutions that determine who is allowed to build, deploy, and sell them.

The moat moves to permission.

The Institutional Inevitability

Semiconductor competition became export controls. Telecommunications competition became trusted vendor lists. Pharmaceuticals became regulatory exclusivity. Aviation became certification.

AI is mid-transition right now—and the mechanism isn’t hypothetical. Consider a parallel data point: when the Commerce Department issued an export control directive extending controls beyond physical hardware directly to model weights and API access, it marked an unprecedented step. While distinct from the Moonshot IP dispute, the directive signals the exact same structural shift. This is what semiconductor export controls looked like in year one, before the formal compliance regime hardened.

This dynamic reflects a deeper structural reality: institutions do not merely react after products converge—they often move preemptively to control access before commoditization is complete.

When that happens, these forces compound across three distinct phases:

First, raw capability becomes diffuse as foundational architectures spread.

Second, institutions intervene to allocate advantage through export licenses, restricted vendor lists, and procurement standards.

Third, capital follows the newly created institutional scarcity. Rather than waiting for a judicial ruling, market participants re-evaluate software assets through executive sanctions and compliance frameworks.

Markets adjust gradually through litigation. Institutions can reshape markets almost overnight through export controls, procurement rules, certification, or sanctions. Whether deliberate or emergent, the economic effect is the same: permission becomes harder to obtain than technology itself. By embedding diffuse legal and geopolitical risk into open-source software, incumbents do not need to win on API pricing; they simply make using the alternative too risky for enterprise compliance departments.

The New Competitive Arena

The Moonshot episode is less important for the specific code extraction than for the operational reality it laid bare: the initial systemic defense was institutional, not technical. AI competition is becoming as much about sovereignty as software.

When capability is scarce, engineers run the market. When capability becomes cheap and pervasive, policy frameworks dictate who gets to build.

If this framework holds, AI competition will increasingly be fought through trusted vendor programs, sovereign AI initiatives, procurement frameworks, certification regimes, export controls, and compliance standards. Model quality will still matter, but institutional positioning will matter more than it does today.

We like to believe markets reward the best technology. Increasingly, they reward whoever defines the rules under which technology is allowed to compete.

Technology determines what is possible.

Institutions increasingly determine what is profitable.

Markets never eliminate scarcity. They relocate it.

The moat has moved to permission.