Last-write-wins
Last-write-wins is the conflict-resolution rule Syndik8 applies to most synced tables. If two devices edit the same record while offline and then reconnect, the write with the later timestamp replaces the earlier one. There is no three-way merge.
The exception is bookings. Overlapping confirmed bookings do not resolve last-write-wins — they are rejected by the database’s exclusion constraint. The first confirmed booking to reach the server is accepted; the second is rejected and surfaces as a sync error on the second device.
Last-write-wins is appropriate for edits where the loss of the earlier change is a minor surprise (a note rewrite) but unacceptable for edits where two conflicting values would be a category error (a booked slot). Syndik8 picks per table.