Capacity comes first.
Weights-only capacity is parameter count multiplied by quantized precision. At 500B and 2-bit weights, that is 125 GB before runtime state.
Turn the iPhone 20 NPU-plus-ASIC prediction into constraints you can inspect: weights, memory traffic, and dense compute.
The source values are loaded by default. Change assumptions to explore a future Apple design or a hypothetical Chinese-company design. No future benchmark is implied.
These formulas are deliberately inspectable. Real inference adds KV cache, activations, runtime overhead, and memory movement, while sparsity, MoE routing, caching, and speculative decoding can reduce work.
Weights-only capacity is parameter count multiplied by quantized precision. At 500B and 2-bit weights, that is 125 GB before runtime state.
The optimistic stream bound assumes one full weight pass per generated token and perfect reuse beyond that pass.
The common dense-decoder estimate is roughly two operations per active parameter per generated token.
Architecture names do not decide a benchmark. Memory packaging, thermal limits, power, software, active parameter count, and silicon utilization decide what survives outside a slide.
Exactly 500B parameters and 50 TPS. This is the post's prediction translated into a measurable constraint set.
A labeled assumption set, not a leaked iPhone specification. Adjust its bandwidth and compute to discover the break-even point.
A parallel hypothetical, not a composite benchmark for Chinese companies. The same formulas keep the comparison honest.
50 TPS is an outcome. The chip diagram is only the beginning of the explanation.
Export the current scenario, formulas, gaps, and caveats as a durable hardware brief.