Release
Public evaluate pipeline and report schema v1
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 - First public GitHub and PyPI release
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 the immutable release record, read the tagged CHANGELOG.md for v0.2.0.
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.