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.

1 files changed, 3 insertions, 0 deletions

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