Release
Proof packs v2 + role-based adapters that feel more natural
Adapters move to role-based routing, proof packs become easier to inspect (v2 layout), and reporting output gets a readability upgrade.
Release: InvarLock 0.3.7 — Better outputs, better workflows, less friction
Highlights
- Role-based adapter routing (instead of model-name adapters).
- Proof packs v2 layout + scenario manifest + verdict generation.
- Reporting output refreshed (Markdown/HTML/glossary) and notebook smoke checks added.
0.3.7 is one of those releases where nothing is “flashy,” but you feel it every time you run bigger suites. Adapters moving to roles makes the system line up more closely with how people actually reason about model families, capabilities, and wiring—less special-casing, more consistency.
Proof packs also level up: the v2 layout and scenario manifest make the output more browseable, and the added verdict generation helps the results read more like an outcome and less like a folder full of artifacts. Reporting got a polish pass too, so the “what happened?” view is easier to scan and share.
If you run notebooks as part of your workflow, the smoke runner is a small but welcome guardrail—it helps prevent quiet drift in docs/examples from becoming a surprise later.
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.