Release
The first public release
The initial public release on GitHub and PyPI: core evaluate pipeline, guard chain, schema v1, and the first docs/CLI surface.
Release: InvarLock 0.2.0 — The foundation everything else builds on
Highlights
- Core compare/evaluate pipeline + guard chain.
- Report schema v1 + usable CLI entry points.
- Torch-optional install with extras + initial docs.
This is the starting line: the first time the whole idea is available publicly as a cohesive tool, not just a repo of experiments. 0.2.0 ships the core evaluate loop and guard chain, plus the report schema and CLI surface that makes it usable without living in the codebase.
It also sets the tone for versioning expectations: until 1.0.0, minor releases can include breaking changes. That’s not a warning so much as a “this is moving fast” label—so upgrades should be deliberate, not accidental.
If you’re new to InvarLock, this is the release that gives you the baseline mental model for everything that follows.
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.