Replacement carries the complete payload; partial edits are patches

Context

Replacement and partial editing need distinguishable contracts. Silent treatment of omissions makes integration behavior difficult to predict.

Decision

The existing planning ruling remains the source of the complete-payload requirement. Interaction replacement implements it, while task and configuration mappings retain different omission behavior. This examination does not change their planning rules.

Alternatives Considered

The structured alternatives describe concrete competing designs and their tradeoffs. Where the origin records an existing ruling, it remains the authority; an observed implementation does not establish Product’s rejection of every alternative.

Consequences

Alignment would change behavior for clients using omission to clear values. Console task and interaction field edits use patches, while configuration screens also use replacement saves.