The research question
One user removes an obsolete customer note while another edits an offline copy. On reconnection, blindly preferring the edit resurrects information that someone deliberately deleted; blindly preferring deletion discards new work. The correct interpretation depends on the application and evidence, so the synchronization layer should not hide the competing intentions behind a simple timestamp rule. Bayou explores application-specific conflicts and tentative writes in weakly connected systems. Its relevance here is the need to distinguish delivery, convergence and an acceptable business interpretation when independently edited records meet again.
A concrete design choice
The proposed model treats deletion as a durable revision or tombstone with causal context. A concurrent edit remains available as a conflict, while an edit that clearly follows an authorized deletion needs an explicit restoration operation. The review shows the relevant versions and preserves the decision taken. Garbage collection must retain enough deletion history to prevent an old replica from reintroducing removed content after a long absence. Local text can be quarantined for review when it cannot be accepted into current shared state, avoiding both silent loss and automatic resurrection.
What would demonstrate usefulness
Test edit-then-delete, delete-then-authorized-restore and genuinely concurrent delete/edit sequences. Deliver them in different orders and reconnect an old replica. Check that the visible outcome and retained evidence match the intended semantics rather than depending on network timing or whichever file happened to arrive last.