b70-optimization-lab

Shared-gate component threshold miss

Date: 2026-07-23 EDT / 2026-07-24 UTC

Classification

This packet and artifact root are terminal and must not be reused.

Exactness and dispatch

The marked M=8 shared-gate path used one torch.mm call with zero torch.bmm or fallback calls and exactly matched its literal raw-BF16 reference. The M=1-through-M=7, unmarked M=8, and marked-prefill controls stayed on their required torch.bmm paths.

All 128 distinct pre-timing epochs and all 32 distinct post-timing epochs reported both raw_uint16_equal=true and torch_equal=true for every comparison. The timing preflight also established raw equality among the literal BMM, literal MM, preallocated control output, and preallocated candidate output before any warm-up or timed arm.

Frozen timing result

The valid isolated primitive protocol used:

The native M=8 BF16 MM candidate beat the literal stride-zero B=8/M=1 BF16 BMM control in all 31 of 31 blocks. Savings ranged from 0.103621140625 ms to 0.133871273437 ms per 47-call cycle, with:

The win-count condition passed, but the median-saving condition did not. No block individually reached the frozen 0.150 ms saving. The stable positive signal does not override the preregistered threshold and is not an accepted optimization.

Preserved campaign evidence

Decision

Do not rerun this packet and do not weaken the frozen threshold. The simple shared-gate BMM-to-MM substitution is a reproducible sub-threshold positive, not a bankable component win. Any follow-up must make a materially stronger candidate—such as a separately justified combined occupancy change or a deeper shared-expert kernel improvement—and preregister its own acceptance rule before device measurement. This result alone does not authorize counters or an endpoint benchmark.