Yesterday's signals, distilled — A look back at March 10.
Gas turbines in Mississippi. A $1B “world model” seed. Oracle’s AI-fueled earnings defense. A $5B memory R&D center. A frontier lab turning safety, policy, and strategy into one institute while fighting a Pentagon blacklist.
On the surface, it’s scattered: energy, chips, models, governance, and a few “boring” verticals quietly compounding.
Underneath, it’s one story: AI is exiting the software frame and hardening into infrastructure — power plants, memory fabs, industrial compute org charts, and policy institutes with real teeth.
If you’re still treating AI as a feature line item in your product roadmap, you’re misaligned with where capital is actually going: long-duration, power-constrained, policy-entangled systems that will not be easy to unwind.
Your plan is probably over-rotated to models and under-rotated to energy, memory, and governance.
⸻
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.
⸻
INFRASTRUCTURE / ENERGY
Gas turbines are now part of the AI stack
Former Climate Hero Wins Permit for 41 Gas Turbines in Mississippi — Forty-one new gas turbines were approved to power data centers in Mississippi, explicitly tied to hyperscale compute demand, per Gizmodo.
This is fossil generation built as a direct response to data center growth — not generic grid capacity.
The Bet: Hyperscale AI demand will stay high enough, long enough to justify locking in gas-heavy generation for years.
So What?
AI capacity is now visibly coupled to local fossil buildout. That shifts AI from an abstract “cloud” story to a physical infrastructure story that regulators, activists, and communities can point at — specific plants, specific emissions, specific permits.
If your product depends on hyperscale AI, you’re now downstream of energy politics and local permitting risk. Your brand is implicitly co-branded with the generation mix of your cloud region, whether you acknowledge it or not.
The Risk:
Backlash against “AI-powered gas plants” can translate into moratoria, delayed permits, or forced offsets that change your unit economics mid-flight.
If regulators start tying AI workloads to specific environmental obligations, your cost of compute stops being just a cloud line item and becomes a compliance and PR liability.
Action:
• Map your AI workloads to specific regions and their generation mix — know exactly how “green” or “brown” your capacity really is.
• Pressure-test your roadmap against a scenario where your preferred regions hit permitting delays or face new carbon pricing.
• Start building an energy narrative — and procurement strategy — that you’d be comfortable explaining to a skeptical board and a hostile journalist.
⸻
SEMIS / MEMORY
Memory is the next hard choke point
Applied Materials partners with Micron and SK Hynix to develop next-gen memory chips for AI and HPC at its new EPIC center, part of a planned $5B R&D investment, per Reuters.
The EPIC center is structured as a long-horizon R&D hub focused on memory technologies tuned for AI and high-performance compute — bandwidth, density, and energy efficiency.
The Bet: The bottleneck shifts from raw FLOPs to memory bandwidth and capacity — whoever controls advanced memory wins the next cycle of AI and HPC economics.
So What?
Model performance and cost are increasingly memory-bound. Context windows, retrieval-heavy architectures, and world models all lean on fast, dense memory more than on marginal GPU TOPS.
If you’re designing models, hardware, or large-scale inference services and you’re not optimizing around memory constraints, you’re building for a world that is already gone.
The Risk:
Assuming “more GPUs” solves your scaling problems ignores the reality that memory supply, packaging, and thermal limits will cap what you can actually deploy.
If your architecture assumes cheap, abundant HBM or equivalent, you’re exposed to a single-point failure in the supply chain that you don’t control.
Action:
• Sit your infra and ML leads down this week and ask one question: “Where are we memory-bound today?” Document the answer.
• Prioritize model and system changes that reduce memory footprint — quantization, sparsity, retrieval design — over chasing marginal model size.
• In vendor conversations, push for transparency on memory roadmaps and packaging constraints, not just GPU counts and list prices.
You’re reading the preview.
The full daily continues with additional rail sections, each with sourced signal reads and operator action items.
Sign up free to read the full daily →