Quantization-aware adapters and safe device movement

Release: InvarLock 0.3.0 - Capabilities metadata, auto-routing, and broader coverage

Highlights

• Quantization metadata and detection (methods/config/capabilities).
• Safe device movement to avoid .to() foot-guns on quantized models.
• Smarter auto-adapter routing + broader tests.

0.3.0 is foundational if you’re working with quantized or pre-quantized checkpoints. Instead of treating quantization like a weird edge case, the framework can represent it, detect it, and route adapters appropriately—so you spend less time fighting “why did this load differently?” issues.

The safe device movement work is especially practical: it helps avoid a common class of runtime errors where models manage device placement internally and don’t tolerate generic .to() calls.

If you’ve been building guard/eval workflows across different quantization setups, this release is essentially the “make this feel normal” moment.

Sources

Website documentation explains the maintained workflow. The changes described here belong to InvarLock v0.3.0; the tagged release record preserves that historical scope.

• Documentation
• Tagged v0.3.0 changelog