Training compute

node

The total arithmetic performed to train a model, conventionally reported in floating-point operations, and the field's only widely comparable input measure. It is an estimate rather than a reading: for most models it is reconstructed from hardware counts, run durations and utilisation assumptions, because developers rarely publish it. Its usefulness is that it is the quantity everything physical attaches to — accelerator supply, capital expenditure, electricity, land and cooling water all scale with it — and its danger is that it is easy to treat as a proxy for capability when the mapping between them has never been stable. Regulators have nonetheless adopted compute thresholds, because a number that can be estimated from procurement is administrable in a way that a capability claim is not. That is a decision about tractability, not a finding about what the number means.

A node is not a place. Drawing it on a map would assert something about the world that no stored fact supports.