Versioned record replacement contract

Context

This record cites an existing write standard, not an implemented guarantee. The service contracts preserve current behavior and its findings rather than silently making the code conform through specification text.

Purpose-specific workspace protection does not imply that every status or commercial field is absent from every customer replacement.

Decision

Carry the cited standard’s complete editable replacement and client-held version requirements into preparation, while keeping current missing-version, patch and optional-definition-version deviations explicitly recorded.

Alternatives Considered

Preserve omitted editable fields during replacement. That would collapse replacement into patch semantics and remove omission-based clearing required by the standard.

Consequences

Current deviations include server faults for missing replacement versions, server-read patch comparisons, optional definition versions and metadata changes on no-op saves.

Workspace lifecycle and commercial-reference changes are protected from ordinary saves; staff status and customer commercial fields follow their distinct implemented permissions.

Replacement clearing needs direct behavioral proof before the implementation can claim conformance.