22 SEPTEMBER 2026 · THESIS UPDATE
The link between compute, geography and energy is becoming operational
The new evidence is easier to interpret once the underlying layers are clear. The next section therefore reconstructs the system from demand down to power.
The Fujian–Ningxia pilot adds an execution example spanning the control plane, network, data centre and power layers. National monitoring and Xiong’an platform reach are separate evidence streams, with separate tests for commercial value.
Read the evidence and implications →AI demand & models
Demand originators and model ecosystems.
Explore →LAYER 02Control plane
Cloud, runtime and workload scheduling.
Explore →LAYER 03Compute / memory
Accelerators, DRAM, HBM and the storage hierarchy.
Explore →LAYER 04Interconnect
Scale-up links, optical systems, wide-area networks and private networking.
Explore →LAYER 05AIDC
Operators, facility technology suppliers and captive developers.
Explore →LAYER 06Power & energy
Storage, power electronics, cooling and grid access.
Explore →The site is about the system. Companies are evidence of how its interfaces are being built.
These interfaces are where the thesis becomes testable: a company matters when it provides evidence that two layers are actually being connected.
Every relationship is now classified first by the infrastructure problem it helps us observe. This keeps the project from becoming a collection of company profiles: architecture defines the question; corporate relationships provide evidence; economics determines whether the relationship matters.
DEMAND × CONTROL PLANE
Why: convert application demand into schedulable, monetizable compute. Cases: Xiaomi × KC; ByteDance × Volcano Engine.
DEMAND × HETEROGENEOUS COMPUTE
Why: keep AI output scaling despite fragmented accelerator supply. Case: ByteDance × Huawei/Cambricon/Iluvatar.
COMPUTE × NETWORK
Why: make separated resources behave more like usable pools. Case: VNET × Huawei/DYXnet.
AIDC × ENERGY
Why: turn electricity into reliable AI-ready MW. Case: VNET × CATL.
ENERGY × POWER ELECTRONICS
Why: deliver high-density electrical architecture to AI racks. Case: CATL × Zhongheng.
ENERGY × CONTROL PLANE
Why: optimize the physical energy/computing system itself. Case: CATL × DeepCtrls.