Did this 20 years ago in an FMMS. It's not worth it. It's better to have an arbiter source of truth that can guarantee ACID principles with transactions rather than introduce merge conflicts or lose transactions for lack of synchronization. The internet is almost everywhere, so use that rather than provide academic features that cause more headaches than they solve. SQL databases with transactions and row locks are invaluable inventions.
Also, if you want to collaborate, synergize, innovate, and revolutionize consider OTs. They're a known quantity. Handling merges of data is fraught with landmines.
You can't sell 2 of something to the same person offline and know if they wanted 1 or 2. Plus, giving an end user the ability to resolve merge conflicts is asking for theft and fraud.
Also, if you want to collaborate, synergize, innovate, and revolutionize consider OTs. They're a known quantity. Handling merges of data is fraught with landmines.
You can't sell 2 of something to the same person offline and know if they wanted 1 or 2. Plus, giving an end user the ability to resolve merge conflicts is asking for theft and fraud.