Changes Are Made Against the Version Read

Context

The recorded shared version policy requires current versions for field-changing writes and preserves metadata on unchanged saves. Regional implementation meets only part of that policy.

Decision

Replacement and patch of definitions or individual rules require versions. Settings accept omission, deletion has no version, and accepted updates increment versions even without a business change. These observed exceptions remain proposals or gaps, not additional approved choices.

Alternatives Considered

Require a settings version for every save. Unsaved settings currently return no version, which explains the code exception but does not approve it permanently; an initial-version contract could resolve this.

Allow all writes without version checks. That would contradict the recorded shared concurrency policy and permit lost edits.

Consequences

An omitted settings version permits overwriting newer settings. Unchanged accepted updates still advance versions and timestamps contrary to the no-op policy. Unversioned deletion can remove a record changed since the caller last read it.