docs: define sync conflict semantics
This commit is contained in:
parent
02969ac7af
commit
24a0a3d153
5 changed files with 186 additions and 14 deletions
|
|
@ -221,12 +221,12 @@ Goal: make convergence and failure behavior predictable enough for automation.
|
|||
- `[ ]` Tests cover partial stream failure.
|
||||
- `[ ]` Tests cover duplicate records and stale cursors.
|
||||
|
||||
- `[ ]` Define per-resource conflict semantics.
|
||||
- `[x]` Define per-resource conflict semantics.
|
||||
Acceptance criteria:
|
||||
- `[ ]` CAS/file-root conflict semantics are documented and tested.
|
||||
- `[ ]` KV conflict semantics are documented and tested.
|
||||
- `[ ]` Document merge semantics are documented and tested.
|
||||
- `[ ]` DB change application limits are documented and tested.
|
||||
- `[x]` CAS/file-root conflict semantics are documented and tested.
|
||||
- `[x]` KV conflict semantics are documented and tested.
|
||||
- `[x]` Document merge semantics are documented and tested.
|
||||
- `[x]` DB change application limits are documented and tested.
|
||||
|
||||
- `[ ]` Add live-sync retry and backoff policy.
|
||||
Acceptance criteria:
|
||||
|
|
|
|||
Loading…
Reference in a new issue