Release
Calibration, determinism, and regression protection
`invarlock calibrate` arrives, determinism utilities mature, and regression harness + golden tracking help prevent silent policy drift.
Release: InvarLock 0.3.2 - First-class calibration and golden-output tracking
Highlights
- New calibration CLI (
invarlock calibrate) and tuning modules. - Determinism flows for repeatable presets and runs.
- Regression harness + tracked golden to catch silent gate/output shifts.
This is the release where calibration stops being “something you do around InvarLock” and becomes something the framework supports directly. Having invarlock calibrate as a first-class command makes tuning policies and guard behavior feel more systematic—and easier to explain to other people.
Determinism utilities also get a serious boost here, which matters if you care about repeatability beyond a single machine or day. And the regression harness + golden tracking is the quiet hero: it’s basically insurance against subtle drift. If something shifts in gates or outputs, you want to catch it early—before it becomes a messy “which commit changed this?” hunt.
For the immutable release record, read the tagged CHANGELOG.md for v0.3.2.
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.