Yesterday's signals, distilled.

Yesterday's signals, distilled, A look back at March 9.

Compute as comp. World models funded like a late‑stage IPO. Sovereign and city governments underwriting entire ecosystems. GPU vendors moving up into assistants and orchestration.

The common thread isn’t “more AI.” It’s who owns the levers: capacity, capital, and coordination.

Compute is turning into a budget line for talent, not just workloads. Frontier labs are no longer the only gravity wells, cities, sovereigns, and new foundations are building parallel stacks. And the integration layer, assistants, orchestration, “OS for work”, is where lock‑in will actually live.

If your plan still assumes you’re choosing “a model” or “a cloud,” you’re behind. The real decision now is: which stack do you want to be structurally dependent on, and what, if anything, do you own outright?

BLUF

At Neue Alchemy, we support leaders navigating inflection points, when tech, capital, and policy converge. If your roadmap is already in motion and you're pressure-testing execution, we're open to conversations.

We also reserve capacity for education, SMBs, and mid-market leaders, those starting, mid-flight, or seeking outside perspective before systems harden.

TALENT / COMPUTE

Compute is becoming compensation, and governance.

Business Insider reports that Silicon Valley leaders are actively exploring “AI compute as compensation”, giving top engineers dedicated inference capacity as part of their pay package, per Business Insider.

The idea is simple: instead of only cash and equity, you grant access to a slice of GPU time or tokens on internal models that engineers can use for side projects, research, or internal experiments.

The Bet: Top technical talent values privileged access to frontier‑grade compute as much as incremental cash, and will optimize their employer choice accordingly.

So What? This turns headcount planning into capacity planning. You’re no longer just budgeting salary and options, you’re allocating scarce inference capacity as a talent retention tool. That forces a real answer to “who controls our GPUs?”, HR, infra, or product. It also blurs the line between corporate and personal R&D: if an engineer builds something valuable on “their” compute, IP ownership and upside participation become live issues, not hypotheticals.

The Risk: If you treat compute as a perk without clear governance, you invite IP disputes, shadow products, and security exposure. Over‑allocating to talent also risks starving core product teams of capacity in crunch periods, turning a recruiting advantage into an execution bottleneck.

Action: • Quantify your real, fungible compute budget per FTE and decide what, if any, slice you’re willing to earmark as “personal R&D” capacity. • Draft a one‑pager this week on IP,