Read the explanation
The executable default has seventy point six billion parameters, not the unused seventy-billion fixture. At sixteen bits per weight, storage is one hundred forty-one point two decimal gigabytes. At three bits, it is twenty-six point four seven five. Both bars use three pixels per decimal gigabyte. This parameter count times bits divided by eight estimates assigned weight bytes. It does not measure output quality, allocator usage, or checkpoint compatibility. The cache equation multiplies keys and values, eighty layers, eight KV heads, a fixed one hundred twenty-eight head dimension, and two bytes per value. Dividing by two to the thirtieth makes four thousand ninety-six context tokens require one point two five gibibytes; doubling context makes two point five. Both bars use one hundred eighty pixels per gibibyte. The source uses binary cache units alongside decimal weights, so its final sum is a planning heuristic, not a unit-consistent allocator measurement. Ordinary quantization branches add point two gigabytes of overhead. The Trellis branch instead adds four point five percent of its weights plus point two five. On twenty-six point four seven five weight gigabytes, that gives one point four four one three seven five. Both bars use three hundred pixels per assigned overhead gigabyte. Including cache and activation, the default total is about thirty, and the hardware fit check also reserves one extra gigabyte. The assigned quality score is a heuristic, not a measured benchmark.