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/architecture.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'docs/architecture.md') diff --git a/docs/architecture.md b/docs/architecture.md index d867d4a..9edf086 100644 --- a/docs/architecture.md +++ b/docs/architecture.md @@ -55,7 +55,8 @@ the node names its types as `document` re-exports them (`Document`, `ChangeHash` `Change`, `ActorId`) and works through `document`'s functions. Two views of it: * **The store** (`document::store`): JSON over slash-separated paths, with Automerge's - concurrent values merged into one view (maps union, scalars newest-wins) and + concurrent values merged into one view (maps union, scalars newest-wins; where the + policy asks for signed values, a signed value by its `seq` before anything else) and reported on request (`?conflicts=true`). The HTTP API and the remake kinds work through it; nothing else reads Automerge objects directly. Within a list, a path segment is an index (`servers/0/name`); a negative one counts from the end. A key with `/` in it, or -- cgit v1.3.1