aboutsummaryrefslogtreecommitdiffstats
path: root/src/remake/api.rs
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 /src/remake/api.rs
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 'src/remake/api.rs')
0 files changed, 0 insertions, 0 deletions