The research question
Two account managers edit the same customer note while disconnected. One laptop’s clock is a day ahead, so a latest-timestamp rule would always select that version, regardless of which information is more relevant. The timestamp is useful diagnostic context, but it does not establish whether one edit incorporated or superseded the other. 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 revision model records parent revisions so the system can distinguish a later edit of known content from two independent branches. Concurrent versions remain available for comparison rather than being discarded by clock order. A reviewer can combine compatible information or choose a version with a recorded reason. The resulting resolution identifies the heads it addressed, preventing an unseen third edit from being silently overwritten. Physical time can still help explain when users worked, but the causal relationship between revisions determines whether the system has enough information to treat one as a successor to another.
What would demonstrate usefulness
Create concurrent edits with deliberately skewed clocks and deliver them in different orders. Confirm that the same competing versions remain visible and no text disappears because of timestamp sorting. Then resolve the conflict and verify that every device can identify the exact revisions covered by that decision.