API Versioning

Scope Boundaries

• Use when compatibility policy, deprecation lifecycle, or version transition strategy is in scope.
• Use proactively when API diffs alter semantics, required fields, response shape, or transport guarantees.
• Use when internal and external consumers have different support windows or migration constraints.
• Do not use for first-pass endpoint/schema design without change impact context.
• Do not use for storage internals; use db-*.

Goal

Deliver explicit compatibility governance so consumers can migrate without surprises.