A Placement Write Advances the Version Only When the Region Moves

Context

Placement follows record saving. Advancing versions for invisible input bookkeeping would make the caller’s fresh record version stale without a visible regional change.

Decision

Entities regional persistence compares existing and new references within the update. A changed region advances record metadata; fingerprint-only maintenance preserves it. Ordinary saves omit the fingerprint and cannot erase that independent processing state.

Alternatives Considered

Increment record metadata for every regional persistence write. A deciding-address edit can produce the same region, and needless version increments would invalidate a caller’s just-saved version.

Leave versions unchanged even when placement moves. An editor could overwrite an unseen regional change without a concurrency refusal.

Consequences

Clients need a fresh read before overwriting a changed regional value. Fingerprint-only updates may be captured internally but do not create an address reaction or increment visible record metadata.