97
sync conflict
Two edits of the same row while offline. You must pick a rule: merge, reject, or ask.
What is sync conflict?
A sync conflict is two writers changing the same record without seeing each other. Last-write-wins is a rule. Field merge is a rule. Asking the user is a rule. Silence is data loss.
Why does sync conflict matter when vibe coding?
Models queue offline writes and POST them later. The second device overwrites the first with no message. Name the rule before the queue exists.
How do you do sync conflict?
Version or updated_at on the row. On push, if the server version moved, apply the rule. Surface a conflict state. Do not drop the local edit on the floor.
How do you ask a model for sync conflict?
When syncing (object), detect conflicts with a version. If the server changed, (keep server / keep local / ask). Never overwrite silently. Show a conflict state.
What goes wrong with sync conflict?
Last-write-wins on a shared checklist. The other person’s checks vanish. That is a product bug with a technical name.