Versioned Replacement with Patch Exceptions

Context

Staff edits need clear treatment of omitted fields and protection from overwriting another editor’s work.

Decision

Most configuration saves replace a complete record at its read version; campaigns, codes and recommendation rules accept versioned named-field changes.

Alternatives Considered

Make every operation a partial merge. Complete replacement gives omitted purchasing settings a defined return to defaults.

Accept the last arriving write. That would silently replace another editor’s changes.

Consequences

Replacement forms submit the full saved configuration, including values not currently edited. Owned collections reconcile with their parent, retaining row identities where dependencies need them. Operational counters can change without advancing the staff edit version.