Updates from the InvarLock project, including release changes, CLI updates, docs changes, and practical notes on how to read or ship evaluation evidence.
Latest post: July 27, 2026 across 21 active tags.
Release
InvarLock 0.14.0 adds evaluator-neutral qualification and a recipient-controlled acceptance handoff while preserving verifier-owned replay and permanent v0.13 compatibility.
Release
InvarLock 0.13.0 replaces the former guard-and-report workflow with a closed paired request, canonical signed evidence, independent verifier replay, and one authenticated report path.
Evidence Note
InvarLock's AIware '26 paper shows how InvarLock reports can feed artifact readiness, stop-depth analysis, and host-parity gates without widening the claim beyond release governance.
Research Note
Structural checks matter because they prevent obviously broken edits from reaching evaluation. They do not, by themselves, show that an edit preserved quality.
Release
InvarLock 0.12.1 tightens the Mistral guard-value evidence contract, promotes targeted spectral/RMT/VE probes to required detections, and replaces the attention control with a stock-cap-clean 1.05x lane.
Release
InvarLock 0.12.0 adds knowledge/self-edit workflow metadata, widens BYOE edit-lane evidence, and reorganizes public evidence around backend compatibility and larger model findings.
Evidence Note
Even when an evidence pack is strict, signed, and marked PASS, it is still a portable verification bundle. It does not answer every scientific, safety, or deployment question a reader might ask.
Research Note
Archiving a model-edit decision is not about saving more files. It is about preserving the exact bundle another reviewer would need to re-check the result later.
Release
InvarLock 0.11.0 makes human reports more consistent, separates guard warnings from hard failures, and expands the public evidence surface across model families.
Research Note
A screenshot can communicate a result. An evidence pack can be inspected, checked, and re-verified later. That is the difference between presentation and portable evidence.
Research Note
A strong evaluation result should carry its runtime provenance with it. In InvarLock, that means the runtime manifest travels next to the report and is rechecked by invarlock verify.
Release
InvarLock 0.10.0 makes public evidence packs more explicit, adds signer-authenticity checks, and expands optional quantized-subject adapter validation.
Research Note
An evaluation report is strongest when it is treated as a stable evidence contract: a small required core, meaningful optional blocks, and a clear boundary around what still lives outside the JSON.
Research Note
Calibration is not just analysis around the product. It changes how thresholds are derived, when correction paths may turn on, and which policy values later govern reports.
Release
InvarLock 0.9.0 adds strict assurance mode, fail-closed verifier checks, runtime provenance guidance, and maintainer evidence gates for release review.
Research Note
Calibration becomes operational when sweep artifacts end in reviewable YAML patches that later appear as resolved runtime policy in reports.
Research Note
Variance equalization is stronger when it must earn enablement through predictive evidence, explicit tier knobs, and report-visible provenance.
Research Note
Thresholds are stronger when they come from measured null behavior and end in a policy patch, not from knob-tuning folklore.
Research Note
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
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
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.
Release
InvarLock 0.7.2 simplifies the public release surface around immutable source tags plus the PyPI wheel and sdist, with docs and verification gates aligned around that path.
Research Note
A model-edit benchmark number is only as strong as the comparison behind it. Pairing makes the comparison inspectable.
Release
InvarLock 0.7.1 makes wheel-only verify/report workflows first-class, ships a public contract bundle, and tightens supply-chain and release-validation gates.
Release
InvarLock 0.7.0 adds first-class GPT-OSS support, pilot Ministral 3 8B/14B presets, and a CUDA-capable attested runtime path for GPU hosts.
Research Note
A narrow claim can be stronger than a broad one. InvarLock is about auditable regression risk from weight edits, not general model safety.
Release
InvarLock 0.6.0 adds a shipped Gemma 4 E2B text lane, phase-1 multimodal evaluation, and a unified `--assurance attested|trusted-local` workflow.
Release
InvarLock 0.5.1 adds a push-gated tiny attested smoke lane, a scheduled GPT-2 canary lane, and package-native Ed25519 evidence pack signatures.
Release
InvarLock 0.5.0 adds offline release-verification bundles, package-native evidence-pack verification, and a simplified public CLI centered on evaluate, verify, and report.
Release
InvarLock 0.4.0 stabilizes contracts around policies, evidence packs, and evaluation provenance while tightening verification, CI, and coverage enforcement.
Release
Split-module coverage thresholds now protect critical CLI/reporting paths while config, plugin, report, overhead, and observability edge cases fail closed more reliably.
Release
A focused hardening release: safer AWQ plugin discovery, stronger quantization clipping behavior, and broader report-schema acceptance for edge payloads.
Release
Evidence packs add new showcase and evidence artifacts, while CI and release flows become more deterministic and easier to validate repeatedly.
Release
A stability-focused release: cleaner report output, safer offline evidence-pack flows, and CI/test hardening after the report rename.
Release
A terminology reset (report/evaluate), stricter evidence-pack verification, and a clean upgrade path for Hugging Face Transformers v5.
Release
Adapters move to role-based routing, evidence packs become easier to inspect (v2 layout), and reporting output gets a readability upgrade.
Release
Reports now record and enforce estimator measurement contracts under CI/release profiles, and evidence pack suites can cleanly split calibration vs execution.
Release
Evidence packs gain a deterministic bash test suite and better runtime helpers, window selection becomes stable/offline, and perplexity runs get safer around bad token IDs.
Release
CI/release baseline pairing is fail-closed (pairing evidence is required), and adapters reduce peak memory during retries via chunked snapshot/restore.
Release
Token-weighted paired bootstrap lands across the pipeline, strictness toggles expand, and CI/release pairing expectations become explicit and enforceable.
Release
`invarlock calibrate` arrives, determinism utilities mature, and regression harness + golden tracking help prevent silent policy drift.
Release
Fixes a GPU memory leak during reload fallback, hardens B200 scripts, and adds practical controls for acceptance ranges and overhead measurement.
Release
First-class quantization metadata, safer device movement across quantized models, auto-routing based on checkpoint info, and major test coverage expansion.
Release
The initial public release on GitHub and PyPI: core evaluate pipeline, guard chain, schema v1, and the first docs/CLI surface.
Announcement
A quick introduction to InvarLock: evaluate LLM weight edits with statistical guarantees and auditable evidence packs.