CiruStrixLink 0.3.3
Version 0.3.3 restores a clean product boundary for the optional Launch page.
CiruStrixLink reports and manages the packaged GLM pair; it does not inspect
unrelated applications or encode a particular operator's service inventory.
Launch behavior
- Each machine reports its GLM rank, process state, context profile, DFlash
setting, prefix-cache setting, system-memory use, and configured KV cache. - Paired load and unload retain their fixed ordering, readiness checks, bounded
execution, and rollback behavior. - The loader still prevents the portable and NHI forms of this same GLM
deployment from running together. - Other applications and services remain the operator's responsibility and are
outside CiruStrixLink's policy.
Performance wording
DFlash speed varies with how many proposed tokens the target accepts. The
recorded HumanEval 0–9 gate passed 10/10 at 26.10 weighted generated tokens/s.
The exact 65,680-token prose-heavy recovery probe reached 15.12 tokens/s at
k=5, versus 12.16 at k=3 and 9.38 target-only. That recovery request had much
lower draft acceptance and is documented as a stress case, not as the model's
normal decode rate.
Runtime scope
This release changes no model weights, vLLM code, DFlash implementation,
kernel, launch recipe, context profile, KV allocation, or USB4 transport.
Validation
- Complete Go test suite
go vet- Embedded JavaScript syntax validation
- Whitespace checks
- Static Linux amd64 release build
The already-running GLM pair was not stopped, restarted, reconfigured, or sent
validation traffic while this correction was prepared.