Release
Large-model reload stability and B200 controls
Fixes a GPU memory leak during reload fallback, hardens B200 scripts, and adds practical controls for acceptance ranges and overhead measurement.
Release: InvarLock 0.3.1 - Memory cleanup, scheduling fixes, and acceptance controls
Highlights
- GPU memory is freed before reload fallback (reducing OOM risk on big runs).
- B200 scripts hardened (paths, size detection, error propagation).
- New controls for overhead skipping, primary metric acceptance ranges, and large-run proof-pack guidance.
0.3.1 is a large-run stability release. The memory leak fix is the kind of thing you only appreciate after you have watched a reload fallback fail repeatedly at scale: freeing GPU memory before reloading keeps 70B+ runs from turning one recovery path into a second failure.
The B200 updates are in that same category. Preset path resolution, model-size detection, worker error propagation, cleanup traps, and progress monitoring all become less brittle. The added controls (INVARLOCK_SKIP_OVERHEAD_CHECK plus configurable primary-metric acceptance ranges) give CI/release profiles a cleaner way to handle oversized models without editing code or relying on the older tiny-relax escape hatch.
The release also adds the first comprehensive proof-pack guide, which matters because these larger runs are not just about getting to the end: they need to leave behind enough context for someone else to understand what happened.
For the immutable release record, read the tagged CHANGELOG.md for v0.3.1.
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.