diff options
Diffstat (limited to 'docs/federation.md')
| -rw-r--r-- | docs/federation.md | 33 |
1 files changed, 19 insertions, 14 deletions
diff --git a/docs/federation.md b/docs/federation.md index f6415f5..f2a580e 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -278,12 +278,14 @@ too. The relays aren't: in a federated swarm they are each node's configuration document, which nobody may write plain. Nothing constrains them, and a number that makes no sense has the result it has. A -time of nothing is "at once"; a limit of nothing lets nothing more in. Three end -deciding itself: a `fractions.decide` of 1, `limits.proposals` at 0, a `window` of -nothing. What is left then is refusing that decision, or going apart. A proposal that -leaves a number without a value where it needs one is no proposal. More than a share -is strictly more; a share of the voters, for what was seen for long, is the fewest -voters that are that share at least, and one at least. +time of nothing is "at once": a `final` of nothing makes a claim final as soon as a +third of the voters' nodes stamp, and lets no cut bring back anything given up. A +limit of nothing lets nothing more in. Three end deciding itself: a `fractions.decide` +of 1, `limits.proposals` at 0, a `window` of nothing. What is left then is refusing +that decision, or going apart. A proposal that leaves a number without a value where +it needs one is no proposal. More than a share is strictly more; a share of the +voters, for what was seen for long, is the fewest voters that are that share at least, +and one at least. Where this text says two thirds and a third, it means the two fractions as recommended. What is promised of decisions is argued for those; a swarm that sets @@ -585,8 +587,9 @@ from anyone brings it back. A user gives itself up by a `release` of its own creation, signed with a first key. That puts it out by its own word: its names wait, and it is gone once seen so for -`gone`. Until then a cut takes the release back like any other statement, the -voters' cut too, where the first key was stolen. +`gone`. Until then a cut takes the release back like any other statement, the voters' +cut too, where the first key was stolen, whatever `final` says: what an out user had +waits (Cuts, For good). ### Namespaces @@ -870,12 +873,14 @@ What stops counting stays in the document, and every node holds the same. It is out when resolving. In a namespace, where a value that doesn't count replaced one that does, the one that does is read again (Resolving). -**For good.** What doesn't count because it was given up, replaced, left out by a cut -or past its limit, and has been seen so for `final` (Lengths of time), has stopped -counting for good: no cut, no limit raised, nothing brings it back. Not so what -doesn't count only because its user is out, which waits until the user is gone, nor -what a policy no longer covers, which stays aside until it is dropped. A remake leaves -out what stopped counting for good (Remakes). +**For good.** What doesn't count because it was given up, replaced or left out by a +cut, or because it was past its limit already where it was signed, and has been seen +so for `final` (Lengths of time), has stopped counting for good: no cut, no limit +raised, nothing brings it back. Not so what waits: what doesn't count only because its +user is out, until the user is gone (a user that gave itself up is out by its own +word, its creation waiting with it); what only a limit lowered since puts past it, for +as long as the limit is lower; and what a policy no longer covers, which stays aside +until it is dropped. A remake leaves out what stopped counting for good (Remakes). The price: a key above retiring one below with an early cut takes back what that key signed since, a release among them, further back than an unvouch reaches; a vouch or a |
