PostEnterprise & platform

AI infrastructure is starting to look less like cloud procurement. It looks like capacity diplomacy.

The critical object is not only compute, but the contract around compute: priority, cancellation, and what gets degraded first.

Lukman Nuriakhmetov
Lukman Nuriakhmetov
1 min read · June 11, 2026

AI infrastructure is starting to look less like cloud procurement. It looks like capacity diplomacy.

Google paying SpaceX about $920M a month for access to roughly 110,000 NVIDIA GPUs changes how I read AI infrastructure: the critical object is not only compute, but the contract around compute.

In software, we talk about infrastructure as if the hard part is the API. In regulated and high-dependency systems, the harder questions are usually contractual: who has priority, who can cancel, what happens if capacity is late, and which workloads get degraded first.

That is what makes this deal interesting. A 90-day cancellation clause, a delivery dependency on promised GPUs, and bridge capacity for surging Gemini demand say more about the AI market than another benchmark. Compute is becoming something companies lease under strategic uncertainty, not consume from an infinite cloud shelf.

The architecture is only half the story. The capacity agreement is part of the system.

The model is visible. The cancellation clause is where the dependency lives.

Tags: ai-infrastructure · cloud-computing · engineering-leadership · compute

Related thinking

NoteJune 15, 2026

The System Around the Model Started to Matter More Than the Model

Week of June 8, 2026. Five themes where the value kept moving off the model and into the system around it — compute contracts, observable governance, agent runtimes, and the operating model that has to absorb the output. Plus three counter-signals worth holding in tension.

Weekly Read
8 min
NoteAugust 24, 2026

The Model Stopped Being the Interesting Variable

Week of August 17, 2026. Mistral tripled accuracy on financial filings — 26.7% to 86% — by changing how the model searches, not which model searches. Two different models from two different labs got the same roughly threefold lift from the same harness. That pattern ran through the week: authorisation splitting into four separate questions, a token optimisation that cut tokens and raised total cost by half, throughput outgrowing the review capacity around it, and execution moving into shared team channels. The leverage kept turning out to sit outside the model. A scan-layer TL;DR, five themes each with an operator move, one taken deep, three counter-signals, and what to track.

Weekly Read
14 min
NoteAugust 10, 2026

Capability Outran Confirmation

Week of August 3, 2026. Frontier models generated 6,080 security patches and roughly a quarter of them worked — while a plausible-but-wrong hint in the prompt cut the success rate to one in six, and the agents followed the hint over their own evidence. The same gap opened everywhere: peak capability diverging from production reliability, agents that cannot verify themselves, operational data capping what any model can automate, and portable artifacts carrying no portable trust. Production got cheap. Confirming what was produced did not. A scan-layer TL;DR, five themes each with an operator move, one taken deep, three counter-signals, and what to track.

Weekly Read
14 min