From f48302e101b8f6814a32e834259588cd11731957 Mon Sep 17 00:00:00 2001 From: tv Date: Sun, 8 Nov 2026 21:51:29 +0000 Subject: docs: remakes and signed values Review 3, R3, the replace side: a replace or import remake writes its content as it is, at signed places too, so under a strict policy a member majority can put plain values where envelopes were. access.md says that remakes are outside the rule; keeping envelopes at signed places in every kind is postponed to future-work.md. --- docs/access.md | 3 +++ 1 file changed, 3 insertions(+) (limited to 'docs/access.md') diff --git a/docs/access.md b/docs/access.md index be91185..fdcf23c 100644 --- a/docs/access.md +++ b/docs/access.md @@ -423,6 +423,9 @@ that checks, replacing the one there then; nothing within one; and above one, no replacing or deleting what holds one (a map made where there is none yet is fine). So a member writing to its document directly gets nothing there past the others: the registry, the policy and the bans change only as a user who may change them signed. +A remake is outside this: its snapshot is the quorum's, so a `replace` or `import` +remake a majority of members commits writes at signed places whatever its content +holds, plain values too. ### Turning a swarm strict -- cgit v1.3.1