From 90ad9e632520d3bbc22562c0fd4db2584ef2a92c Mon Sep 17 00:00:00 2001 From: tv Date: Sun, 15 Nov 2026 16:49:08 +0000 Subject: store: a signed value chosen by seq is named so Where the policy asks for signed values, a place's value is chosen by `seq`, but conflict reports still called the choice `newestWins`, and the code and the architecture still said "newest" of what a read shows. A report names it `highestSeq`; the rest says "the one a read shows". --- docs/api.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'docs/api.md') diff --git a/docs/api.md b/docs/api.md index a839f74..05abf44 100644 --- a/docs/api.md +++ b/docs/api.md @@ -192,7 +192,8 @@ one of another kind (a map written over a list), it is written anew. `?conflicts=true` on a read answers `{"value": …, "conflicts": [...]}`: every place on the way where concurrent values were resolved, with all candidates and which was -selected (`mergedMaps` or `newestWins`). A later write at that path ends the conflict. +selected (`mergedMaps`, `newestWins`, or `highestSeq` for a signed value where the policy +asks for them). A later write at that path ends the conflict. ## Following changes -- cgit v1.3.1