The datapath multiplies integer mantissas and applies the shared block scale at
the boundary of a block. The theorem in this chapter is deliberately exact:
for every block length and every starting offset, the integer MAC followed by
one scale multiplication equals the direct scaled dot.
Scoping, stated plainly (review R5): blockMac_correct is an algebraic
identity over arbitrary integer scales — it captures why a shared-exponent
block may defer its scale to the block boundary (scale once, not per MAC), and
nothing more. It does not model exponents, mantissa widths, rounding, or a
bit-level block-float representation; those obligations belong to the encoded
block format and land with the wide-kmac block contract (PLAN milestone 5).
What is fixed-width-faithful today is the mantissa path underneath it: the
kernel chapter proves the machine's kmac loop computes the exact integer
dot product (kmac_loop_exact), so the only unmodeled step between hardware
and this identity is the boundary scale itself.
The default Honeycomb block size is 32, but the theorem is not tied to that value.
The concrete block-size-32 example below is a build-time smoke test.