Release
Bigger proof-pack coverage with stronger CI reproducibility
Proof packs add new showcase and evidence artifacts, while CI and release flows become more deterministic and easier to validate repeatedly.
Release: InvarLock 0.3.10 - More coverage, stronger evidence
Highlights
- Proof packs add a guard showcase suite, expanded scenario filtering/overrides, and new evidence artifacts like verdict table generation plus a VE probe sidecar.
- CI and release verification are tighter and more reproducible, with deterministic
verify-full, Python 3.12 smoke coverage, and scheduled weekly verification. - Mixture-of-Experts and variance/VE paths are hardened for broader model compatibility, with additional reliability fixes across proof-pack packaging and evaluation handling.
0.3.10 grows the practical surface area of proof-pack validation while tightening the behavior around failure handling and evidence quality. The goal is simple: when a run succeeds, the supporting artifacts should be clear; when it fails, it should fail closed with useful context.
This release also continues hardening around CI repeatability so local and remote verification paths converge more closely.
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.