aboutsummaryrefslogtreecommitdiffstats
path: root/docs/access.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/access.md')
-rw-r--r--docs/access.md13
1 files changed, 10 insertions, 3 deletions
diff --git a/docs/access.md b/docs/access.md
index b2cdb70..b64bd21 100644
--- a/docs/access.md
+++ b/docs/access.md
@@ -474,9 +474,9 @@ over first (`continuum-signed verify` on each entry). From then on nothing is ad
the time before: a change written under a policy that isn't strict is refused, received
or held, unless it is in the history of the change that wrote the strict policy, so a
member can't plant at that time what nobody could follow; a node that took one beside
-that change drops it once a peer tells it so (Changes judged on every node, below). A value there that isn't an envelope
-starts its chain anew: any envelope its user once signed for that path replacing
-nothing (`prev` empty) can be put there again. Without the policy, signed values may
+that change drops it once a peer tells it so (Changes judged on every node, below). A
+value there that isn't an envelope starts its chain anew: any envelope its user once
+signed for that path replacing nothing (`prev` empty) can be put there again. Without the policy, signed values may
be written all the same, and plain ones too.
Keep two users who may manage users, or two keys each: under a strict policy, a
@@ -489,6 +489,13 @@ 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.
+But "may" is read where a change was written, which its writer chooses: a capability
+revoked, a user disabled or a key removed holds against members that weren't members
+before it, not against one that was, with a user that could sign then. That member can
+commit, at a history from before, an envelope the user signed then, numbered after what
+was there then, and the next after it, as far as it likes; the place's value is then
+the one with the highest `seq`. A remake ends it: nothing is written at a history from
+before the new epoch.
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.