Evidence packs v2 and role-based adapter routing
Adapters move to role-based routing, evidence 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).
- Evidence 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.
Evidence 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 in Release
Continue through nearby posts in the same reading thread.
Release
Evaluation reports, strict evidence packs, and Transformers v5
A terminology reset (report/evaluate), stricter evidence-pack verification, and a clean upgrade path for Hugging Face Transformers v5.
Release
Measurement contracts for CI and release verification
Reports now record and enforce estimator measurement contracts under CI/release profiles, and evidence pack suites can cleanly split calibration vs execution.
Release
Report rename cleanup and offline evidence-pack hardening
A stability-focused release: cleaner report output, safer offline evidence-pack flows, and CI/test hardening after the report rename.