Release
Quantization-aware adapters and safe device movement
First-class quantization metadata, safer device movement across quantized models, auto-routing based on checkpoint info, and major test coverage expansion.
Release: InvarLock 0.3.0 - Capabilities metadata, auto-routing, and broader coverage
Highlights
- Quantization metadata and detection (methods/config/capabilities).
- Safe device movement to avoid
.to()foot-guns on quantized models. - Smarter auto-adapter routing + broader tests.
0.3.0 is foundational if you’re working with quantized or pre-quantized checkpoints. Instead of treating quantization like a weird edge case, the framework can represent it, detect it, and route adapters appropriately—so you spend less time fighting “why did this load differently?” issues.
The safe device movement work is especially practical: it helps avoid a common class of runtime errors where models manage device placement internally and don’t tolerate generic .to() calls.
If you’ve been building guard/eval workflows across different quantization setups, this release is essentially the “make this feel normal” moment.
For the immutable release record, read the tagged CHANGELOG.md for v0.3.0.
More from the blog
Continue through recent releases and implementation notes.
Synthesis
The Minimum Evidence Surface for Trustworthy Weight-Edit Results
A trustworthy weight-edit result needs more than a benchmark delta. It needs a bounded claim, an exactly paired comparison, and verification that rejects incomplete evidence.
Release
Evidence packs and explicit runtime provenance
InvarLock 0.8.0 moves the public bundle surface to evidence packs, pins docs to versioned release paths, and makes container-vs-host runtime provenance explicit across evaluate and verify.
Research Note
Fail-Closed Verification for Weight-Edit Evaluation
A verifier is only useful if it rejects incomplete evidence. InvarLock's verification path is designed to stop stronger claims when the evidence bundle is missing or inconsistent.