From cc998c1d45939d170bcf8a6512817405ed2b44a3 Mon Sep 17 00:00:00 2001 From: tv Date: Sun, 15 Nov 2026 21:44:19 +0000 Subject: remakes: of one change, its other writes replayed before its links Under a strict policy, links and other writes go by where their change is among those replayed, and of one change the links went first. Both were judged at that change's history, without the other; a link can only take away there what the other writes relied on (a capability revoked), never give what they needed, so they go first now. A group of other writes was placed by its last change by history but named the user of its newest by clock; it names the user of the last by history now, as it goes. --- 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 f7625ef..2d887d5 100644 --- a/docs/remakes.md +++ b/docs/remakes.md @@ -333,7 +333,8 @@ The swarm stays writable throughout. (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), 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. + grants), of one change before its links; 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