aboutsummaryrefslogtreecommitdiffstats
path: root/docs/remakes.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-15 16:41:07 +0000
committertv <tv@krebsco.de>2026-11-15 16:41:07 +0000
commit2d1c64a6e7134f4d6942d4539b27d45f14e7538c (patch)
tree8253ae9782fa3067ae4a75d1cea15840f9d456ba /docs/remakes.md
parent5005b13115caedbe0bda9a8496d95d2b4752c62d (diff)
remakes: values signed by their users replayed as chains
Under a strict policy, a replay wrote at each path the old document's merged view: at a place of a value its user signed, the last envelope alone, whose `prev` names one the new epoch doesn't hold if the value was written twice since the base. Every node refused it, it went to the quarantine, and the new epoch kept the base's value: a remake rolled back every signed value changed twice since its base, and a rejoining node lost its own the same way. And the replay found what changed by Automerge's diff, which says nothing of a value that changed beside Automerge's own choice: where a place held two values at the base, a write replacing the one read by `seq` wasn't replayed at all. Now, under a strict policy, the places of signed values are found from the changes' operations as well as from the diff, and each is replayed as the chain that leads to the envelope the old document reads: every envelope from the one the new document holds there, following `prev` through the changes since the base, each in a change of its own by its signer at the time it was made, judged as every node will judge it. A place is replayed only where the new document holds a lower `seq` there; where no chain leads from what it holds, it goes to the quarantine. A path above such places is split into its keys. Without a strict policy nothing changes.
Diffstat (limited to 'docs/remakes.md')
-rw-r--r--docs/remakes.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/remakes.md b/docs/remakes.md
index 6f4b740..bc53cf2 100644
--- a/docs/remakes.md
+++ b/docs/remakes.md
@@ -325,6 +325,12 @@ The swarm stays writable throughout.
node will judge it, in the new epoch: one they would refuse (its user may no longer
write there, say) goes to the quarantine instead, so it can't cut the carrying node
off.
+* **Values signed by their users**, under a strict policy, are carried over as the
+ chain of envelopes that leads to the one the old epoch reads: each one after what the
+ new epoch holds there, in order, each in a change of its own by its signer, at the
+ time it was made, so that each replaces the one before as every node checks. Not by
+ clocks: a place is carried over only where the new epoch holds a lower `seq` there.
+ Where no chain leads from what it holds, the place goes to the quarantine.
* **Granularity**: map entries are carried over per key. Lists and text are carried
over whole, so concurrent edits of the same list on two nodes around a remake end as
last-writer-wins.