Current on every generation since Hopper
Each generation changes the facility problem before it changes the compute problem. Power per rack, cooling mode and network topology all move, and they move before the hardware arrives. Planning for that shift is the work.
Two classes, delivered whole
Most enterprise requirements resolve to one of two node classes. Both are air-cooled, so both are deployable in conventional contained-air halls with no chilled water to the rack.
One array, two tiers
Most first programmes resolve to the same shape: a knowledge core that trains, fine-tunes and retrieves, and a serving tier that answers in real time. The first-phase array pairs them, entering production as one programme and scaling by tier afterwards.
Four networks, not one
Mixing compute collectives with storage traffic on a shared fabric is the most common cause of a cluster that benchmarks well and trains badly. The reference design keeps them apart.