Version policy

Vision versions each contract boundary deliberately rather than treating one marketing version as authority for every integration surface.

Contract layers

• HTTP API paths and OpenAPI operations
• Machine credential vocabulary (vision-service-credential.v1)
• App API manifests (vision-app-api-manifest.v1)
• Publication projection schemas
• Webhook event names and payloads
• SDK package versions

Compatible changes

Additive optional fields, new operations, new error codes, and new event types may be introduced without changing an existing major version. Consumers must ignore unknown response fields.

Breaking changes

Removing or changing required fields, broadening claim semantics, changing signature input, or altering operation meaning requires a new version and an explicit migration window.