aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/access.md13
1 files changed, 9 insertions, 4 deletions
diff --git a/docs/access.md b/docs/access.md
index 1b40ed2..1f9b1b4 100644
--- a/docs/access.md
+++ b/docs/access.md
@@ -310,10 +310,15 @@ node's actor is forged, refused, and logged as its sender's (`A peer brought cha
forged`). A member can then no longer write as another member; the user a change names is still its node's word.
Whatever the policy, and without one, a change is refused that Automerge itself
-wouldn't have written: bytes that aren't Automerge's encoding of the change, a first
-operation not numbered one after the highest of its dependencies, an operation that
-names one nobody made before it (an object written into, a value replaced). Automerge
-applies some of those, and then panics or saves a document that doesn't load.
+wouldn't have written: bytes that aren't Automerge's encoding of the change; a first
+operation not numbered one after the highest of its dependencies; a change that isn't
+its actor's first and doesn't build on the one before; an operation naming one that
+wasn't made in the change's own history, or that isn't what it is named as (the
+object written into, the element of that list, a value replaced at that place).
+Automerge applies some of those, and then panics, saves a document that doesn't
+load, or holds another change than the one it was given. All of it is asked of the
+change and its history alone, so two nodes that hold a change's history come to the
+same, whatever else they hold.
In a swarm without a registry, whatever a user would need, any member may. A refused
change stays out, and so does whatever builds on it; the node logs it (`Refused a