<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>InvarLock Blog</title><link>https://invarlock.ai</link><description>Release notes, tutorials, and updates from InvarLock.</description><item><title>Report outlines, guard warnings, and wider public evidence</title><link>https://invarlock.ai/blog/release-0-11-0</link><guid>https://invarlock.ai/blog/release-0-11-0</guid><pubDate>Tue, 16 Jun 2026 00:00:00 GMT</pubDate><description>InvarLock 0.11.0 makes human reports more consistent, separates guard warnings from hard failures, and expands the public evidence surface across model families.</description></item><item><title>Evidence Packs, Not Screenshots</title><link>https://invarlock.ai/blog/evidence-packs-not-screenshots</link><guid>https://invarlock.ai/blog/evidence-packs-not-screenshots</guid><pubDate>Mon, 15 Jun 2026 00:00:00 GMT</pubDate><description>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.</description></item><item><title>Runtime Manifests and Why Provenance Must Travel With the Result</title><link>https://invarlock.ai/blog/runtime-manifests-and-why-provenance-must-travel-with-the-result</link><guid>https://invarlock.ai/blog/runtime-manifests-and-why-provenance-must-travel-with-the-result</guid><pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate><description>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.</description></item><item><title>Evidence packs, authenticity, and quantized-adapter validation</title><link>https://invarlock.ai/blog/release-0-10-0</link><guid>https://invarlock.ai/blog/release-0-10-0</guid><pubDate>Wed, 03 Jun 2026 00:00:00 GMT</pubDate><description>InvarLock 0.10.0 makes public evidence packs more explicit, adds signer-authenticity checks, and expands optional quantized-subject adapter validation.</description></item><item><title>What Belongs in evaluation.report.json</title><link>https://invarlock.ai/blog/what-belongs-in-evaluation-report-json</link><guid>https://invarlock.ai/blog/what-belongs-in-evaluation-report-json</guid><pubDate>Mon, 01 Jun 2026 00:00:00 GMT</pubDate><description>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.</description></item><item><title>Calibration Is the Product Surface, Not a Side Utility</title><link>https://invarlock.ai/blog/calibration-is-the-product-surface-not-a-side-utility</link><guid>https://invarlock.ai/blog/calibration-is-the-product-surface-not-a-side-utility</guid><pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate><description>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.</description></item><item><title>Strict assurance and runtime provenance</title><link>https://invarlock.ai/blog/release-0-9-0</link><guid>https://invarlock.ai/blog/release-0-9-0</guid><pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate><description>InvarLock 0.9.0 adds strict assurance mode, fail-closed verifier checks, runtime provenance guidance, and maintainer evidence gates for release review.</description></item><item><title>From Sweep Outputs to Tier Policy</title><link>https://invarlock.ai/blog/from-sweep-outputs-to-tier-policy</link><guid>https://invarlock.ai/blog/from-sweep-outputs-to-tier-policy</guid><pubDate>Mon, 18 May 2026 00:00:00 GMT</pubDate><description>Calibration becomes operational when sweep artifacts end in reviewable YAML patches that later appear as resolved runtime policy in reports.</description></item><item><title>Variance Enablement Should Be Evidence-Gated</title><link>https://invarlock.ai/blog/variance-enablement-should-be-evidence-gated</link><guid>https://invarlock.ai/blog/variance-enablement-should-be-evidence-gated</guid><pubDate>Mon, 11 May 2026 00:00:00 GMT</pubDate><description>Variance equalization is stronger when it must earn enablement through predictive evidence, explicit tier knobs, and report-visible provenance.</description></item><item><title>Null Sweeps as Threshold Derivation, Not Tuning Folklore</title><link>https://invarlock.ai/blog/null-sweeps-as-threshold-derivation-not-tuning-folklore</link><guid>https://invarlock.ai/blog/null-sweeps-as-threshold-derivation-not-tuning-folklore</guid><pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate><description>Thresholds are stronger when they come from measured null behavior and end in a policy patch, not from knob-tuning folklore.</description></item><item><title>The Minimum Evidence Surface for Trustworthy Weight-Edit Results</title><link>https://invarlock.ai/blog/the-minimum-evidence-surface-for-trustworthy-weight-edit-results</link><guid>https://invarlock.ai/blog/the-minimum-evidence-surface-for-trustworthy-weight-edit-results</guid><pubDate>Mon, 27 Apr 2026 00:00:00 GMT</pubDate><description>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.</description></item><item><title>Evidence packs and explicit runtime provenance</title><link>https://invarlock.ai/blog/release-0-8-0</link><guid>https://invarlock.ai/blog/release-0-8-0</guid><pubDate>Thu, 23 Apr 2026 00:00:00 GMT</pubDate><description>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.</description></item><item><title>Fail-Closed Verification for Weight-Edit Evaluation</title><link>https://invarlock.ai/blog/fail-closed-verification-for-weight-edit-evaluation</link><guid>https://invarlock.ai/blog/fail-closed-verification-for-weight-edit-evaluation</guid><pubDate>Mon, 20 Apr 2026 00:00:00 GMT</pubDate><description>A verifier is only useful if it rejects incomplete evidence. InvarLock&apos;s verification path is designed to stop stronger claims when the evidence bundle is missing or inconsistent.</description></item><item><title>Tag-based publishing with slimmer release verification</title><link>https://invarlock.ai/blog/release-0-7-2</link><guid>https://invarlock.ai/blog/release-0-7-2</guid><pubDate>Wed, 15 Apr 2026 00:00:00 GMT</pubDate><description>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.</description></item><item><title>Why Paired Evaluation Beats Before/After Benchmarks</title><link>https://invarlock.ai/blog/why-paired-evaluation-beats-before-after-benchmarks</link><guid>https://invarlock.ai/blog/why-paired-evaluation-beats-before-after-benchmarks</guid><pubDate>Mon, 13 Apr 2026 00:00:00 GMT</pubDate><description>A model-edit benchmark number is only as strong as the comparison behind it. Pairing makes the comparison inspectable.</description></item><item><title>Standalone contract bundles with tighter release gates</title><link>https://invarlock.ai/blog/release-0-7-1</link><guid>https://invarlock.ai/blog/release-0-7-1</guid><pubDate>Sun, 12 Apr 2026 00:00:00 GMT</pubDate><description>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.</description></item><item><title>GPT-OSS pilots with CUDA-ready attested lanes</title><link>https://invarlock.ai/blog/release-0-7-0</link><guid>https://invarlock.ai/blog/release-0-7-0</guid><pubDate>Thu, 09 Apr 2026 00:00:00 GMT</pubDate><description>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.</description></item><item><title>What InvarLock Actually Claims</title><link>https://invarlock.ai/blog/what-invarlock-actually-claims</link><guid>https://invarlock.ai/blog/what-invarlock-actually-claims</guid><pubDate>Mon, 06 Apr 2026 00:00:00 GMT</pubDate><description>A narrow claim can be stronger than a broad one. InvarLock is about auditable regression risk from weight edits, not general model safety.</description></item><item><title>Gemma 4 pilot lanes with a clearer assurance contract</title><link>https://invarlock.ai/blog/release-0-6-0</link><guid>https://invarlock.ai/blog/release-0-6-0</guid><pubDate>Sat, 04 Apr 2026 00:00:00 GMT</pubDate><description>InvarLock 0.6.0 adds a shipped Gemma 4 E2B text lane, phase-1 multimodal evaluation, and a unified `--assurance attested|trusted-local` workflow.</description></item><item><title>Attested smoke lanes with package-native evidence pack signing</title><link>https://invarlock.ai/blog/release-0-5-1</link><guid>https://invarlock.ai/blog/release-0-5-1</guid><pubDate>Thu, 02 Apr 2026 00:00:00 GMT</pubDate><description>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.</description></item><item><title>Offline release verification with a slimmer public CLI</title><link>https://invarlock.ai/blog/release-0-5-0</link><guid>https://invarlock.ai/blog/release-0-5-0</guid><pubDate>Wed, 25 Mar 2026 00:00:00 GMT</pubDate><description>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.</description></item><item><title>Stable public contracts with stricter fail-closed verification</title><link>https://invarlock.ai/blog/release-0-4-0</link><guid>https://invarlock.ai/blog/release-0-4-0</guid><pubDate>Sat, 14 Mar 2026 00:00:00 GMT</pubDate><description>InvarLock 0.4.0 stabilizes contracts around policies, evidence packs, and evaluation provenance while tightening verification, CI, and coverage enforcement.</description></item><item><title>Coverage floors and fail-closed CLI/reporting paths</title><link>https://invarlock.ai/blog/release-0-3-12</link><guid>https://invarlock.ai/blog/release-0-3-12</guid><pubDate>Fri, 27 Feb 2026 00:00:00 GMT</pubDate><description>Split-module coverage thresholds now protect critical CLI/reporting paths while config, plugin, report, overhead, and observability edge cases fail closed more reliably.</description></item><item><title>Quantization, spectral, and report-schema hardening</title><link>https://invarlock.ai/blog/release-0-3-11</link><guid>https://invarlock.ai/blog/release-0-3-11</guid><pubDate>Thu, 12 Feb 2026 00:00:00 GMT</pubDate><description>A focused hardening release: safer AWQ plugin discovery, stronger quantization clipping behavior, and broader report-schema acceptance for edge payloads.</description></item><item><title>Evidence pack showcase coverage and reproducible CI</title><link>https://invarlock.ai/blog/release-0-3-10</link><guid>https://invarlock.ai/blog/release-0-3-10</guid><pubDate>Sun, 08 Feb 2026 00:00:00 GMT</pubDate><description>Evidence packs add new showcase and evidence artifacts, while CI and release flows become more deterministic and easier to validate repeatedly.</description></item><item><title>Report rename cleanup and offline evidence-pack hardening</title><link>https://invarlock.ai/blog/release-0-3-9</link><guid>https://invarlock.ai/blog/release-0-3-9</guid><pubDate>Tue, 03 Feb 2026 00:00:00 GMT</pubDate><description>A stability-focused release: cleaner report output, safer offline evidence-pack flows, and CI/test hardening after the report rename.</description></item><item><title>Evaluation reports, strict evidence packs, and Transformers v5</title><link>https://invarlock.ai/blog/release-0-3-8</link><guid>https://invarlock.ai/blog/release-0-3-8</guid><pubDate>Mon, 02 Feb 2026 00:00:00 GMT</pubDate><description>A terminology reset (report/evaluate), stricter evidence-pack verification, and a clean upgrade path for Hugging Face Transformers v5.</description></item><item><title>Evidence packs v2 and role-based adapter routing</title><link>https://invarlock.ai/blog/release-0-3-7</link><guid>https://invarlock.ai/blog/release-0-3-7</guid><pubDate>Thu, 22 Jan 2026 00:00:00 GMT</pubDate><description>Adapters move to role-based routing, evidence packs become easier to inspect (v2 layout), and reporting output gets a readability upgrade.</description></item><item><title>Measurement contracts for CI and release verification</title><link>https://invarlock.ai/blog/release-0-3-6</link><guid>https://invarlock.ai/blog/release-0-3-6</guid><pubDate>Tue, 13 Jan 2026 00:00:00 GMT</pubDate><description>Reports now record and enforce estimator measurement contracts under CI/release profiles, and evidence pack suites can cleanly split calibration vs execution.</description></item><item><title>Deterministic evidence packs and safer perplexity runs</title><link>https://invarlock.ai/blog/release-0-3-5</link><guid>https://invarlock.ai/blog/release-0-3-5</guid><pubDate>Fri, 02 Jan 2026 00:00:00 GMT</pubDate><description>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.</description></item><item><title>Fail-closed baseline pairing with lower-memory retries</title><link>https://invarlock.ai/blog/release-0-3-4</link><guid>https://invarlock.ai/blog/release-0-3-4</guid><pubDate>Sun, 28 Dec 2025 00:00:00 GMT</pubDate><description>CI/release baseline pairing is fail-closed (pairing evidence is required), and adapters reduce peak memory during retries via chunked snapshot/restore.</description></item><item><title>Token-weighted paired statistics and stricter release gates</title><link>https://invarlock.ai/blog/release-0-3-3</link><guid>https://invarlock.ai/blog/release-0-3-3</guid><pubDate>Sun, 21 Dec 2025 00:00:00 GMT</pubDate><description>Token-weighted paired bootstrap lands across the pipeline, strictness toggles expand, and CI/release pairing expectations become explicit and enforceable.</description></item><item><title>Calibration, determinism, and regression protection</title><link>https://invarlock.ai/blog/release-0-3-2</link><guid>https://invarlock.ai/blog/release-0-3-2</guid><pubDate>Sun, 14 Dec 2025 00:00:00 GMT</pubDate><description>`invarlock calibrate` arrives, determinism utilities mature, and regression harness + golden tracking help prevent silent policy drift.</description></item><item><title>Large-model reload stability and B200 controls</title><link>https://invarlock.ai/blog/release-0-3-1</link><guid>https://invarlock.ai/blog/release-0-3-1</guid><pubDate>Wed, 10 Dec 2025 00:00:00 GMT</pubDate><description>Fixes a GPU memory leak during reload fallback, hardens B200 scripts, and adds practical controls for acceptance ranges and overhead measurement.</description></item><item><title>Quantization-aware adapters and safe device movement</title><link>https://invarlock.ai/blog/release-0-3-0</link><guid>https://invarlock.ai/blog/release-0-3-0</guid><pubDate>Fri, 05 Dec 2025 00:00:00 GMT</pubDate><description>First-class quantization metadata, safer device movement across quantized models, auto-routing based on checkpoint info, and major test coverage expansion.</description></item><item><title>Public evaluate pipeline and report schema v1</title><link>https://invarlock.ai/blog/release-0-2-0</link><guid>https://invarlock.ai/blog/release-0-2-0</guid><pubDate>Mon, 01 Dec 2025 00:00:00 GMT</pubDate><description>The initial public release on GitHub and PyPI: core evaluate pipeline, guard chain, schema v1, and the first docs/CLI surface.</description></item><item><title>Welcome to InvarLock</title><link>https://invarlock.ai/blog/welcome-to-invarlock</link><guid>https://invarlock.ai/blog/welcome-to-invarlock</guid><pubDate>Sun, 30 Nov 2025 00:00:00 GMT</pubDate><description>A quick introduction to InvarLock: evaluate LLM weight edits with statistical guarantees and auditable evidence packs.</description></item></channel></rss>