1. Confirm that customers can pin usage to a specific, immutable model version identifier. If so, describe your versioning scheme and the guarantee of immutability (i.e., that underlying weights and inference configuration will not change for a pinned version).
Why it matters. Stable, pinnable model versions are foundational for production reliability. Vendors may silently swap model weights behind a stable identifier, breaking customer workflows that were validated against a prior version. This question verifies the vendor's commitment to immutability, a critical control for managing behavioral drift and ensuring repeatable outcomes.
- Explicitly confirms customers can pin to an immutable version identifier
- Describes a clear versioning scheme (e.g., semantic, dated snapshots)
- Distinguishes between immutable (pinned) versions and floating aliases (e.g., 'latest')
- Only offers floating aliases with no option to pin
- Reserves the right to make silent updates behind a stable identifier
- Ambiguous definition of what constitutes a 'version'