Actionable insights — The Trillion-Dollar Off Switch

1. Score every AI player on the build-vs-rent axis — then add shutdown risk

1. For any company with AI exposure, classify it: does it build a frontier model or rent one? Building buys control and upside; renting makes the model a swappable component.
2. Add the third variable the old framework missed: regulatory-shutdown risk — the chance a government can pull a deployed model from the market overnight.
3. Re-rate accordingly: a builder carries more upside but more concentration risk; a renter sheds the CapEx arms race and most of the shutdown exposure, at the cost of differentiation.

• A company whose entire value rests on one model it owns, versus one that can swap models — the tell for where shutdown risk concentrates.

2. Apply the "cushion test" to a frontier-model owner

1. For a model owner, ask: if the model were switched off tomorrow, what revenue would still be standing?
2. A diversified owner (search, app store, cloud, ads) has a cushion that absorbs the blow; a pure-play lab has none — the model is the business.
3. Discount the pure-play's valuation for that single point of failure even when its model is the best.

• The share of a model owner's revenue that survives a model recall; concentration into a single deployed asset.

3. Read AI lateness as a possible hedge, not just a miss

1. When a company is behind in AI, check whether it solved the gap by renting a model rather than building one.
2. Quantify the rent (the annual fee) against the CapEx it avoids — a ~$1B/yr bill versus tens of billions of data-center spend can be a feature.
3. Credit the renter for sidestepping commoditization and shutdown risk; debit it for losing control of the core experience and any region where the deal can't ship.

• A laggard quietly licensing a rival's model; the annual fee vs the avoided CapEx; regions where the rented feature can't legally launch.

4. Track the regulatory-recall precedent as a new systemic variable

1. Treat the first government recall of a deployed commercial AI as a precedent that re-prices every frontier owner, not a one-off.
2. Monitor three signals: how fast the affected model's access is restored, whether other labs receive similar directives, and whether the government formalizes a repeatable model-recall framework.
3. Widen the risk discount on pure-play owners as those signals harden; narrow it if the episode proves isolated.

• A second lab receiving a directive, or a written model-recall rule — either turns a one-off into a sector-wide risk premium.

5. Flag dual-use capability as the trigger for intervention

1. Gauge how close a model's capabilities sit to genuine national-security concern (e.g. finding exploitable flaws in operating systems and browsers).
2. The more dual-use the capability, the higher the odds of an off-switch — capability and regulatory risk rise together for a frontier owner.
3. Note who the vetted partners are: a model restricted to a small defensive program signals the capability regulators most fear.

• Frontier capabilities with offensive-security uses; access deliberately gated to vetted partners — the marker of a model a government may pull.