From 79f17df285e376892c691b7a27f90a89cf8a32ea Mon Sep 17 00:00:00 2001 From: tv Date: Fri, 13 Nov 2026 03:25:50 +0000 Subject: screen: a change refused after its checks stands in for nothing Screening checks that a change is one Automerge writes (`changes::Written`) before it looks for forks and judges the rules, and the checks recorded what a change made as soon as it passed them. A fork of a change the document holds has its actor and counters: if it was checked first in a batch, and refused as forged after, its record stood in for that change's operations, outside the history of the next. An honest change writing into what the real one made was then refused, for good. Anyone could make such a fork, its hash ground to sort first. What a change made is recorded once screening takes it (`Written::taken`), and an operation named is looked for in the batch and in the document, whichever the change's history holds. --- docs/access.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'docs/access.md') diff --git a/docs/access.md b/docs/access.md index 1f9b1b4..dd87d3c 100644 --- a/docs/access.md +++ b/docs/access.md @@ -318,7 +318,8 @@ 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. +same, whatever else they hold: a change of the same batch refused after it passed +(forged, or against the rules) stands in for nothing. 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 -- cgit v1.3.1