Read versions and creation recovery have operation-specific exceptions

Context

Lost responses can conceal successful saves, while stale forms can overwrite newer work. The recorded policy addresses both through read versions and creation recovery.

Decision

Console creation chooses its identifier before sending. Interaction replay additionally compares a stored digest while the row exists. Ordinary edits and public task lifecycle actions use versions, but the title’s broad policy has the documented implementation exceptions.

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

Recovery avoids repeated live-row interaction creation. Clients must follow the contract of each operation rather than assume every write has identical version or repeat semantics.