Source audit done, before the harness. One defect, one ambiguity settled.
The reference is now available — transformers from main
(5.17.0.dev0) in a venv on beast reusing the system…
The step-7 ambiguity is settled: our reading was right
Recorded here because this issue is where the question was raised, and it was raised as needing a reference trace. It did not — it…
Two more guards a guarded window needs, both learned by breaking things
Five qwen4_exp cold-load windows on beast (2026-09-06/07) found two failure modes beyond the wrong-restore-spec this…
quant means two different things depending on the load path, so in-situ quantisation is unreachable on a single GPU
quant means two different things depending on the load path, so in-situ quantisation is unreachable on a single GPU
Fixed and confirmed live on beast (1ae3ba72).
Both halves of this issue are observable in the journal of a real cold load of the model that found it:
06:57:08 no GGUF in this repo;…
First slice landed and validated against the real checkpoint
1ae3ba72 on main. The n-gram table is no longer made resident
anywhere: the 128 shards are mapped where they already lie in…
Arithmetic correction: the experts are 73.0 GB, not 67.9
bf1e80ed claimed to meet the 640-wide reduction "the way llama.cpp
meets the same wall". It did not. Upstream's tensor_type_fallback…
Two corrections and a boundary worth drawing before anyone designs this.
The GGUF claim above is wrong — withdraw it
I wrote that "our ISQ is not bit-identical to theirs and the substitution…
The residency paragraph above — "either pinned resident on beast or it is not served" — is presented as an operator decision, and #322 is why it currently is not one.
Measured on beast…