docs: define sync conflict semantics
This commit is contained in:
parent
02969ac7af
commit
24a0a3d153
5 changed files with 186 additions and 14 deletions
|
|
@ -445,6 +445,8 @@ validity, and representative peer grants when local metadata is available. Use
|
|||
|
||||
See `docs/automation-examples.md` for shell, Python JSON, and user-service
|
||||
automation examples.
|
||||
See `docs/conflict-semantics.md` for the current per-resource conflict behavior
|
||||
used by CAS/file roots, KV, documents, DB sync, and signed metadata logs.
|
||||
|
||||
## Owner And Node Management
|
||||
|
||||
|
|
@ -666,6 +668,8 @@ stability rules for CLI commands, `--json` output, the local control JSONL
|
|||
protocol, Iroh peer wire protocols, SQLite metadata, and signed operation logs.
|
||||
Command-family stability levels are tracked in
|
||||
[`docs/command-stability.md`](docs/command-stability.md).
|
||||
Per-resource conflict behavior is tracked in
|
||||
[`docs/conflict-semantics.md`](docs/conflict-semantics.md).
|
||||
|
||||
GitHub Actions workflows live under `.github/workflows/`:
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue