The Standing Wave
The Tuesday Signal · Retrospective

Ten weeks in: four tracks, one convergence.

Signal № 010 · Tue 28 Jul 2026 · By Ross Candido · Coverage window: 21–27 Jul 2026 · ~9 min read
The Insight

Ten weeks in, the build-out has not changed direction. Spend is certain; proof of durable returns is not. The contest moved down the stack — from cost-per-watt, to customer conversion, to data trust, to who keeps margin when inference cannot cover the compute bill.

Four tracks carried that arc across nine issues. They converge on one gap: valuations priced for earnings that have not yet survived a full cycle.

The next phase is not another capability race. Watch where the industry shifts attention — customers, retention, consumption — as public markets grade sustained revenue, not hype.

Thesis Dashboard 14 tracked · retrospective read

Weekly hypothesis read (Signal № 010, 2026-07-28): Weekly hypothesis read (Signal № 010, 2026-07-28): Retrospective issue. The issue-level read holds all fourteen hypotheses unchanged; directional movement is narrated across the nine-week arc rather than re-scored on a single week.

H1
H2
H3
H4
H5
H6
H7
H8
H9
H10
H11
H12
H14
H15
Unchanged (retrospective)

The multiples got louder. The rooms did not fill.

Whether the lens is Anthropic, SpaceX, OpenAI, the hyperscalers, or the application layer, the same dust is in the air — and it will not settle while competition is still accelerating. Models keep improving; cost mechanics keep shifting to capture share. The access line still decides which horses get more backing. Public investors are already reading through the hype to what sits underneath: revenue that lasts.

Read the arc together and the same thing is missing week after week: a proven book of business. Capability is very strong across the board. What no company in this build-out yet holds is durable revenue — contracts signed at a price both sides can model, that have survived a full pricing cycle. These businesses are a year deep on data and priced a decade out on valuation. A high multiple is a bet on earnings that last; when the earnings are real but young, the multiple is a hope with a number attached. That gap, between the price and the proof, is the issue.

This week extended the arc rather than breaking it. Moonshot's Kimi K3 reset the price floor from the East, Anthropic stood up a services venture to reach customers directly, and New York halted large data-centre construction outright. Each is the next tick on one of the four tracks below.

Four tracks, one convergence.

Here is where the four tracks meet. Spend is certain and compounding. The model advantage is dissolving into open weights. Three strategies that share no rulebook are fighting for the market. Power binds all of it, and the bill reaches the household as surely as the hyperscaler. The one thing that would justify the valuations — revenue proven to last — has mostly not had time to exist. Every track bends to the same point: price climbing while the foundation stays young.

You have seen this shape before. A capability wave hits, capital floods in, prices scatter across the stack, and for a few years nobody can tell which layer keeps the margin. What makes this cycle different is the speed and the size. The spend is large enough to make real casualties, and capability is commoditising fast enough that being best — the usual protection — is gone before the book of business is built. That is the empty-room risk. Not that the read is wrong, but that the multiples are being shouted at a durability that has not yet walked in. The distance between the shouting and the room is the thing to watch from here.

Four tracks across nine issues.

Retrospective arc from Signals 002–009, with this week’s window at the end of each track.

The business-model track

Three ways of charging in ten weeks, and a book of business still unproven.

From SaaS-pocalypse to cost-per-completed-task

H12 App revenue ↑ H2 Financing / digestion ⇆ H10 Deployment ⇆

Watch how the customer was asked to pay, because it changed three times. First the consolidation read: AI would compress the software stack the way every capability wave does, and the labs would push into their customers' businesses to find revenue. Then tokenmaxxing — more tokens looked like more value until the invoice arrived. By midsummer, enterprises were reining in employee AI as metered costs bit; one executive said flatly they had created a monster. Then came the correction in late June and early July: the number that matters is not the token, it is the completed task. Cursor benchmarked Opus at roughly $11 per finished coding job against its own model at 55 cents. The buyer pays for work done, not sticker price.

Under all three sits the read we filed in the first financing window: capital got certain before returns did. Money flowed down the stack into infrastructure while the deployment layer stayed contested, and that contest never resolved. Application revenue was the most-worked hypothesis in the register — the sign of a layer where cash is real, pricing keeps moving, and staying power is untested.

The wider record adds the concession that keeps this honest. Real books of business already exist in pockets: Suncorp scaled AI into claims workflows, Rio Tinto into logistics, and Databricks reached a reported $188 billion valuation on enterprise data it already holds. Those outcomes are genuine. They are not yet widespread, and not what most of these valuations assume. Moving fast was never the question. Moving fast on a foundation no pricing cycle has tested is.

The frontier track

Frontier stopped being a place. It became a download.

From race to open source

H6 China gap ↑ H5 Inference cost ↑ H4 Autonomous ↑

The frontier arc ran in four moves. It began as a race — whoever had the best model won — and at the opening of the arc we read the contest as cost-per-watt at frontier capability. Convergence followed: by early June the top Chinese and US coding models sat within a point of each other, and by midsummer the labs had stopped claiming the model was the constraint, naming their own capability overhang. Open weight came next, with GLM-5.2 shipping at roughly one-sixth of closed-model pricing in late June. This week it sits at open source as deliberate strategy: Kimi K3, open-weight by design, reportedly beating a Western flagship on coding benchmarks and moving markets as it did.

One honest wobble sits in the middle of that arc. Inference cost read both ways for four straight weeks. The China gap logged both ways in the export-control fortnight — not through weakness, but because the order cut two directions at once, concentrating capability in US hands even as it fractured the global market. Calling those weeks clean in hindsight would be the easy lie. The read stayed ambiguous until the evidence closed it.

The wider record adds a qualifier that matters. Open models now lead on volume — nearly half of tracked business tokens on one major router running through Chinese systems, per reported industry data — yet frontier labs still capture most spending, because their prices are higher and buyers keep paying for the hardest jobs. Capability commoditised before revenue did. That is the same shape as the price-versus-proof gap one track over: activity racing ahead of the money underneath it. Once frontier capability is a download, the model stops being a defensible advantage, and that fact drives most of what the other three tracks are sorting out.

The three-way battle

Competition, incumbency, and coordination, fighting over the same market.

Two Western engines and one Chinese one

H15 Vertical integration ⇆ H12 App revenue ↑ H6 China gap ↑

Most coverage frames this as the United States against China. Nine weeks of coverage say it is three-cornered, and the third corner explains this week. Inside the West there are two engines. The labs compete on the frontier — raw capability, speed, and the push into customers' businesses that the compute bill demands, visible this week in Anthropic's services venture. The application incumbents compete on something older: hold on data, customers, and workflow. They spent the week defending it, with Microsoft coaching sellers to knock the labs on cost and trust rather than capability. The week before last we read the labs as cornered rather than predatory, and the incumbents answering.

The third engine is Chinese state coordination, and it plays by neither Western rulebook. It is patient where competition is fast, directional where incumbency is defensive, and it needs no return on the price floor it sets. Kimi K3 and Xi's "AI for all" keynote are not a lab competing on metrics. They are a state playing a longer game: concede cheap inference, set the global floor, and let Western capital strand itself against a price that does not have to make money.

Two concessions keep the frame honest. The corners are porous, not walled. The same companies that fight also partner: Snowflake with the clouds, the labs with the hyperscalers they rent from, OpenAI and Anthropic increasingly with each other. The frame leaves Europe out, which spent the window chasing partial sovereignty rather than picking a side. Neither breaks the read. None of the three engines has won: Western labs bet speed decides it, incumbents bet customer hold outlasts the frontier, China bets a plan outlasts them both. Anyone telling you which wins is guessing.

The constraint underneath

The one track no financing and no ideology can route around.

Power, and the bill the household pays

H3 Power constraint ↑ H7 Grid queues ↑ H9 Turbine lead times ↑

Every track above assumes the machines stay on, and says nothing about who pays when they do. Power was the steadiest call across the run, and it escalated on a schedule. Late May it entered through the ratepayer thread, when PJM wholesale capacity had roughly doubled on data-centre demand. Early June it became a permitting queue, with more than 60 percent of 2027 US capacity not yet under construction. Mid-June it became federal policy when FERC voted to fast-track connections on the operators' terms. Two weeks ago it became a constituency fight — capacity pricing up roughly tenfold across two years, steelmakers on the same grid calling the bill unsustainable.

This week it became law. New York halted large data-centre construction outright: the first statewide moratorium in the nation, and not an outlier but the first to land of many. More than a hundred proposals have surfaced at local, county, and state level, with bipartisan support across fourteen states, and roughly seven in ten Americans say they do not want a data centre nearby, per recent polling.

This is where the story stops being about markets and lands on a person. The electricity a data centre needs is the electricity the household already pays for, and the split is now in the tariffs. In Arizona, the largest utility proposed a 45 percent rate rise for extra-large users that are mostly data centres — and a 14.5 percent rise for ordinary residential customers in the same filing. Read those two numbers together and the politics of the whole build-out sits in one rate case: the industry's bill and the household's bill are climbing together. When a valuation outruns its earnings, the investor carries the risk. When a build-out outruns public consent, the public carries it, and that is the one no IPO can price.

From here.

The empty-room thesis, tested forward. The price-versus-proof gap is the call to grade. Watch for the first signed, multi-year, fixed-price enterprise books that show the revenue lasts, and equally for the first large brand whose multiple cracks because it does not.

The two human edges. The ratepayer edge is on the record: watch tariff cases where the industry's rise and the household's rise sit in the same filing. The labour edge is the watch-item to evidence properly or drop.

Q1 Quarterly Review, Pass 2. Extends the helicopter pass through the first nine issues, narrating where citation volume diverged from the editorial read.

Key sources

Retrospective callbacks trace to Signals 002–009; this week’s window claims (Kimi K3, Anthropic services venture, New York moratorium) per citation log 010.