Replacements carry the complete record at the version read

Context

Replacement omission can silently erase data when an editor fails to send it.

Decision

The design proposes complete payload validation for purchasing replacement alongside existing version checks. The recorded CRM decision supplies precedent, not approval for Commerce.

Alternatives Considered

Documented omission clearing remains vulnerable to incomplete clients. Switching to patch semantics would change the existing replacement contract.

Consequences

Current purchasing schemas still permit omission. Making absence an error needs a scoped product decision and subsequent implementation, rather than claiming it is already enforced.