Back to blog

Release

Report rename cleanup and offline proof-pack hardening

Ink/charcoal doodle: a proof-pack folder feeds an aligned offline report.

A stability-focused release: cleaner report output, safer offline proof-pack flows, and CI/test hardening after the report rename.

1 min read
InvarLock Team

Release: InvarLock 0.3.9 - CI cleanup, report readability, and offline package safety

Highlights

  • CI workflow test paths now match the report/certificate rename.
  • invarlock report explain now prints the resolved drift band and keeps artifact path columns aligned.
  • Proof-pack, observability, packaging, and import-safety paths are more robust offline.

0.3.9 is a practical cleanup release after the report rename. CI workflow tests now follow the new report/certificate paths, and invarlock report explain prints the resolved drift band instead of a hard-coded threshold. The ARTIFACTS block is aligned so report output is easier to scan.

The rest of the release closes operational paper cuts that can make repeatable workflows noisy. CPU health checks no longer fail when platform CPU counts are unavailable, proof-pack config generation can write to stdout without /dev/stdout, the memory-management integration test gets a PyTorch warm-up, wheel packaging can run with build --no-isolation, and import-safety tests skip cleanly when the network is unavailable.

The README branding updates in this release are cosmetic, but they support the same goal: make the public surface clearer while the evaluation/report terminology settles.

For the immutable release record, read the tagged CHANGELOG.md for v0.3.9.

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.