Release
Proof packs v2 and role-based adapter routing
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 - Scenario manifests, verdicts, reports, and notebook smoke checks
Highlights
- Role-based adapter routing (instead of model-name adapters).
- Proof packs v2 layout + scenario manifest + verdict generation.
- Reporting output refreshed, new CLI flags added, and notebook smoke checks protect examples.
0.3.7 is a workflow-shape release. Adapters moving to roles makes routing line up more closely with how people actually reason about model families, capabilities, and wiring: less model-name special-casing, more consistent behavior across causal and mixture-of-experts paths.
Proof packs also level up. The v2 layout, scenarios manifest, assurance verdict generation, tuned-params hygiene, baseline-report reuse, and better memory planning make the output easier to inspect and the suite easier to operate. The added run --edit-label and evaluate --baseline-report flags make those workflows more explicit at the CLI boundary.
Reporting gets a readability pass across Markdown, HTML, and glossary output, while the old “Safety report” language is replaced with “Evaluation report.” The release also broadens presets/overlays, improves Mixtral and weight-tying behavior, and adds notebook smoke checks so docs and examples do not quietly drift away from the CLI.
For the immutable release record, read the tagged CHANGELOG.md for v0.3.7.
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.