Back to blog

Release

Evidence packs and explicit runtime provenance

Ink/charcoal doodle: versioned docs and a runtime shield feed into a checked evidence-pack folder.

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.

2 min read
InvarLock Team

Release: InvarLock 0.8.0 - Evidence packs, versioned docs, and runtime provenance

Highlights

  • The public and maintainer bundle surface is now evidence packs, with CLI, docs, contracts, notebooks, scripts, and packaged public-evidence recipes aligned around invarlock advanced evidence-pack.
  • Evaluation and verification now make the runtime boundary explicit through evaluate --execution-mode container|host and verify --runtime-provenance container|host.
  • Release docs now publish to versioned GitHub Pages paths such as /0.8.0/, while the package carries shipped public evidence under public_evidence/published_basis/....

0.8.0 is a naming and evidence-boundary release more than a broad claim expansion. The old proof-pack surface has been renamed to evidence packs across the public command and documentation set, and the synced site docs now point readers at Evidence Packs and Evidence Pack Internals. If you maintain wrapper scripts, dashboards, or runbooks around the older proof-pack path names, this is the release where those references should be updated.

The release also makes runtime provenance harder to blur. evaluate now describes container versus host execution through --execution-mode, while verify mirrors that boundary with --runtime-provenance. The runtime-manifest verifier output is versioned as runtime-verify-v1, and the verifier lives under the main CLI as invarlock advanced runtime-verify instead of a standalone console script. That keeps the default path centered on the same report bundle: evaluation.report.json plus the adjacent runtime manifest for container-backed runs.

For reviewers, the report surface gets easier to navigate without changing the underlying evidence contract. The HTML export now has summary chips, a quick-link rail, and clearer browser framing, while report explain --evaluation-report can work directly from evaluation-bundle provenance when the linked run reports are available. Underneath that, the upstream release adds more maintainer smoke lanes for runnable docs, installed-wheel front-door flows, and container journeys, and expands the model inventory with the Qwen/Qwen2.5-7B declared experimental lane plus additional deferred candidate surfaces.

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

More from the blog

Continue through recent releases and implementation notes.