From c96470e4a28f69a640812998b8226faa52bc8d38 Mon Sep 17 00:00:00 2001 From: tv Date: Sun, 15 Nov 2026 20:21:11 +0000 Subject: remakes: other writes replayed with the links by history Under a strict policy, the links of the chains to signed values went in the order their changes were made, but the other writes were grouped by time, and a link went before a group only where its time wasn't later. A write built on what a link grants (a capability in an entry its manager signed, a ban lifted, a declaration) went first wherever its clock was behind the link's, was judged where it wasn't granted yet, and was quarantined, though every node had taken it. Under a strict policy the other writes now go by where the last change that wrote them is among those replayed (`between`), with the links, and keep their times for later replays. Without a strict policy there are no links, and the groups go by time as before. --- docs/remakes.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'docs/remakes.md') diff --git a/docs/remakes.md b/docs/remakes.md index 1cb14d1..f7625ef 100644 --- a/docs/remakes.md +++ b/docs/remakes.md @@ -332,7 +332,8 @@ The swarm stays writable throughout. clocks: a place is carried over only where the new epoch holds a lower `seq` there (otherwise as a write that loses), and the links of all places in the order their changes were made, each after those it builds on (one may add the key the next is - signed with); clocks decide only between changes neither of which saw the other. + signed with), and the other writes with them (one may build on a capability a link + grants); clocks decide only between changes neither of which saw the other. Where no chain leads from what it holds, the place goes to the quarantine; where a link is refused, the place keeps the last one taken, and the rest goes to the quarantine. -- cgit v1.3.1