Release
Stability under load (especially at 70B+)
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 — More knobs when reality gets messy
Highlights
- GPU memory is freed before reload fallback (reducing OOM risk on big runs).
- B200 scripts hardened (paths, size detection, error propagation).
- New env vars for overhead skipping and primary metric acceptance ranges.
0.3.1 is a “make the big runs stop hurting” release. The memory leak fix is the kind of thing you only appreciate after you’ve watched a run fail repeatedly at scale—freeing GPU memory before reloading is a simple change with outsized impact.
The B200 script fixes are in that same category: fewer brittle edges, better failure behavior, less guessing. And the added operational knobs (skip overhead checks for large models, configure acceptance ranges without editing code) are there because real pipelines aren’t always neat—sometimes you need control, not ideology.
For more details, see CHANGELOG.md.
More from the blog
Continue through recent releases and implementation notes.
Release
Stable public contracts with stricter fail-closed verification
InvarLock 0.4.0 stabilizes contracts around policies, proof packs, and evaluation provenance while tightening verification, CI, and coverage enforcement.
Release
Coverage hardening across CLI, reporting, and observability paths
Coverage thresholds now enforce split-module branch floors for critical CLI/reporting paths.
Release
Targeted regression hardening for quantization and reporting paths
A focused hardening release: safer AWQ plugin discovery, stronger quantization clipping behavior, and broader report-schema acceptance for edge payloads.