Back to blog

Release

Measurement contracts you can point to

Ink/charcoal doodle: a measurement contract sheet sits beside ruler ticks and a stamped check.

Reports now record and enforce estimator measurement contracts under CI/release profiles, and proof pack suites can cleanly split calibration vs execution.

1 min read
InvarLock Team

Release: InvarLock 0.3.6 — Proof pack runs that are easier to pause and resume

Highlights

  • Guard estimator “measurement contracts” recorded in reports and enforced by verify --profile ci|release.
  • Proof pack suite can split into --calibrate-only and --run-only.
  • B200 calibration defaults avoid CPU SVD bottlenecks by defaulting guard order away from spectral/RMT.

This release is for anyone who’s ever looked at two runs and asked: “Okay, but were these really measured the same way?” 0.3.6 makes that answer easier by recording and enforcing measurement contracts—especially in CI/release verification profiles where ambiguity is the enemy.

It also improves the reality of long suites. Proof packs can now be run in phases: generate calibration outputs first, then come back later to finish execution without turning it into a manual recovery exercise.

And if you’re calibrating on big GPU nodes, the updated defaults are intentionally pragmatic: avoid slow CPU-bound SVD dominating wall time (and making GPUs look idle) unless you explicitly opt back into that calibration path.

For more details, see CHANGELOG.md.

More from the blog

Continue through recent releases and implementation notes.