Daily Pulse · · 10:00 CET · 18 min read · macro · IGV

Circuit-board landscape with a silicon wafer and rising candles: the AI build-out moving from chips to the software that governs what agents may do

From Silicon Scarcity to Software Scarcity: The Next AI Bottleneck Is Permission to Act, and the Market Graded It This Week

In this edition

neutral Temperature 49/100

Holding at 49 / below the 50 line

Index moves

Index1D1W
Rubin 100 ≈-0.6% -5.1%
HALO 100 ≈+0.3% -3.0%
Euro-AI 50 -0.1% -3.9%
AW40 ≈-1.0% -2.0%

Pattern alerts

  • IGV two-day-slide BEARISH
  • SNOW after-hours-bid BULLISH
  • DDOG below-50-day BEARISH
  • QQQ second-close-under-50 WARNING
  • IEF below-veto-line BEARISH

Cointegration

7 active pairs, 7 breaks.

Rubin monetized the scarcity of compute. The software constraint trade has to monetize the scarcity of something less tangible and harder to price: an enterprise's permission for a machine to act. This page sets out the thesis in short form today, the full report follows, and the week's earnings reactions serve as the first live test.

§1 — The thesis in one line

Model capability keeps rising and inference keeps getting cheaper. Neither produces a useful enterprise agent on its own. Before a company lets an agent do anything that matters, the agent has to understand the company's vocabulary, find current information, keep state, obtain permission, coordinate tools and other agents, execute through real workflows, and prove or reverse what it did. The scarce asset is therefore not software code. It is organizational permission to act, encoded in software.

Agent deployment = min { Context · State · Permission · Orchestration · Verification · Recovery } · if one term fails, the agent stays a pilot

The companies worth researching under this thesis own an unavoidable control point somewhere in that loop and can turn agent activity into a billable meter: queries, compute, records, actions, workflows, traces, security events or credits. Data gravity alone is not enough. Owning a chat window is not enough. The vendor has to sit where the agent cannot go around it.

The single most important distinction. A physical constraint, the kind the Rubin 100 was built to track, is investable because supply cannot respond quickly: a fab, a substrate line or a gigawatt of power takes years. A software constraint is investable only when customers cannot bypass the control point. Software layers can develop simultaneously, be bundled, be routed around through open standards, collapse into one incumbent platform, or move between vendors in a quarter. So this is not "Rubin, but in software." It is a more dynamic trade in which the bottleneck migrates, and the portfolio has to be weighted by evidence rather than by narrative purity.

C — free account

The free C account unlocks the full Daily Pulse — every section of this read.

One tap with Google or one email — no password, no card. You are signed in until you sign out, on this browser, from then on.

Join the Look — free

Already joined on this browser? The full edition shows automatically — if it doesn't, sign in again here. Looking for the archive, portfolios and realtime? That is C+.

The signals behind this Each line links to the tool it comes from
Rubin 100 Our 100-name AI build-out index — masked headline, 37 sub-indices from architects to interconnects. Open Rubin 100 →