diff options
| -rw-r--r-- | docs/federation.md | 118 |
1 files changed, 64 insertions, 54 deletions
diff --git a/docs/federation.md b/docs/federation.md index 01f6358..5a6a8d9 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -109,6 +109,10 @@ What is not promised: a claim made out of its sight contests it. After, a root does, by saying it saw another first; and so does anyone, through one honest node of a root or of the claimant that hadn't received the claim yet and is given the other first. +* **A moved-in user against its root.** The root named to give its first keys, while + no other root's node has seen its creation (that day, or with no other root), signs + a twin of it: the two contest, and nothing signed with the keys of either counts + until the voters give first keys. * **A settled name against the roots.** One root contests it. To take it, every root that saw it first has to turn: each cuts off the node that saw it. A final name is out of their reach. @@ -197,12 +201,14 @@ its voters' votes. ### The policy, in the genesis change -A federated swarm's policy is `{"version": 2, "values": "signed", "users": "vouched"}`, -with what the rules read beside it in `_continuum/access`: the kinds of names -(`claims`), the paths in namespaces whose values are signed (`userSigned`, as today), -and the **numbers**. All of it is in the swarm's genesis change, with the roots, the -voters, and the users it starts with. ("Root" here is always a user: an epoch's first -change, the genesis change or a remake's snapshot, is its **root change**.) +A federated swarm's policy is +`{"version": 2, "values": "signed", "users": "vouched"}`, with what the rules read +beside it in `_continuum/access`: the kinds of names (`claims`), the paths in +namespaces whose values are signed (`userSigned`, as today), and the **numbers**. All +of it is in the swarm's genesis change, with the roots, the voters, and the users it +starts with, naming for each that has no keys the root that gives them. ("Root" here +is always a user: an epoch's first change, the genesis change or a remake's snapshot, +is its **root change**.) * Nothing is ever written before the policy, so nothing is judged by none. * Every node is given a root change and takes no other: the genesis change @@ -292,16 +298,19 @@ grows. A statement is signed by one user and says one thing: * **A user the root change holds** has the ID given there, and needs no creation. It may be there without keys (a registry moved in from elsewhere): then it is in, has its name and what the root change holds in its name, and nobody signs for it, until - a root's `create` for that name gives it its first keys. That is no other user. Such - creations are claims of one thing, ordered as claims of a name are (Two claims), - with the roots' nodes alone as their witnesses (a user's nodes carry for it by its - keys, which these decide): one signed in sight of another that stands is refused, - one late against another is late for good, and of two that contest each other - neither gives keys until the voters say which (they give first keys anew: - Decisions). So a root that comes later than another to give keys gives none, and of - two that answer at once, each root's node seeing its own first, neither does. No - root releases its `create`: once one gives keys, they are the user's, which gives - itself up as any user does. + the root the root change names for it gives it its first keys, by a `create` for + that name. That is no other user, and no other root's `create` gives it keys. Should + that root sign two, they are claims of one thing, ordered as claims of a name are + (Two claims), with the other roots' nodes alone as their witnesses (a user's nodes + carry for it by its keys, which these decide; its root's nodes witness for its own): + one signed in sight of another that stands is refused, and one late against another + is late for good. Which one remains is read over all the changes, as for a name, and + not where each statement was signed: a twin on old dependencies gives keys nowhere. + Of two that contest each other (no other root's node saw one first, or two saw them + in two orders), neither gives keys, and nothing signed with the keys of either + counts, until the voters give first keys (Decisions); what was signed with the keys + they give counts then. No root releases its `create`: once one gives keys, they are + the user's, which gives itself up as any user does. * **A user's own name, by its own key.** A user claims its own name as a name of the kind `user`, signed with its own key: a claim of what it has already. It counts toward no limit, a user has one at a time, and it holds the name on where its @@ -1002,8 +1011,8 @@ clocks. A window of days bears clocks that are minutes apart. * **Who votes**: the list of voters, by their IDs, one matter. Recommended, as said above, those who take part. * **Who the roots are**: their IDs, one matter, and for each root it leaves out which - root has each name a rule gives a root. One that names no root is no proposal: - nobody would be in. + root has each name a rule gives a root, and which gives the first keys it was named + to give. One that names no root is no proposal: nobody would be in. A decision stays, whatever is cut off after: a vote signed with a key that is retired later, from before, stays in it. The days a vote takes are the time to cut a stolen @@ -1049,10 +1058,11 @@ of two remakes the nodes go to. * what doesn't count and could still come to: what was given up, replaced, left out by a cut or past a limit, and hasn't stopped counting for good (Cuts), each as its envelope, with what stopped it; - * what the order among claims rests on: which claim gives way to which, which is - late against which, which is settled and which final, which statements count - through an unvouch or a cut; and for each claim not yet settled, the users whose - nodes had it standing in a change they committed; + * what the order among claims rests on (creations among them, and a root's for a + user the root change holds): which claim gives way to which, which is late against + which, which is settled and which final, which statements count through an unvouch + or a cut; and for each claim not yet settled, the users whose nodes had it + standing in a change they committed; * how far each length of time has run: for each thing being seen (a user out, a claim holding its name, a decision holding, a thing uncovered), each node of a voter with its first stamp, and that stamp's time, from which it has held the @@ -1352,7 +1362,7 @@ A proposal's `matter` and what it `holds`: | `whose`, naming a kind and a name | the digest of the claim that is to hold it | | `votersName`, naming a kind and a name | the user ID it is given to | | `voters` | the voters' IDs | -| `roots` | the roots' IDs, and for each root left out which root has each name a rule gives it | +| `roots` | the roots' IDs, and for each root left out which root has each name a rule gives it and which gives the first keys it was named to give | | `fork` | the policy to go on with, and, if it likes, `voters` and `roots` | A fork is no matter: a vote for one counts toward nothing, shows who would go, and @@ -1419,14 +1429,15 @@ A change is valid if, in the document at its dependencies: Nothing replaced, nothing deleted, nor anything that holds a register. 5. A `create`: its name is one the kind `user` takes, and neither a creation of it nor a user's claim of it as its own name stands there, a rule of the kind lets the - signer, and the signer isn't past its limit there; or it is a root's, for a user - the root change holds, that has no keys there. `key`, `node`, `vouch`: not past - their limits there; a `vouch` for a user that isn't gone there. `unvouch`: by the - signer of what it takes back, or by a root for what is the seats'. `retire`, a node - stopping: by a key above, or by the key itself as said under Cuts, the cut in the - change's history, and its list what the key signed within it. `release`: by the - user of what it releases; of the user itself, with a first key; never of a root's - `create` for a user the root change holds. + signer, and the signer isn't past its limit there; or it is by the root named to + give a user the root change holds its first keys, for that user, which has none + there. `key`, `node`, `vouch`: not past their limits there; a `vouch` for a user + that isn't gone there. `unvouch`: by the signer of what it takes back, or by a root + for what is the seats'. `retire`, a node stopping: by a key above, or by the key + itself as said under Cuts, the cut in the change's history, and its list what the + key signed within it. `release`: by the user of what it releases; of the user + itself, with a first key; never of a root's `create` for a user the root change + holds. 6. A `claim`: of the kind `user`, only by the user of that name, of its own name, while no claim of its own of it stands there, where a rule of the kind lets the user create that name. Else the kind is declared, the name is one of it, a rule @@ -1485,24 +1496,22 @@ the steps before: proposal and a vote: always, for a voter); its key was the user's where the statement was signed (added by statements that count, up to its creation, which gives its first keys whether or not it counts as a vouch; for a user the root - change holds, by the root's creation that remains there, the roots' creations - ordered first, by the roots' nodes alone; or given by a decision); it is within - every cut set for that key (by a `retire` that counts, or a decision); a node - committed it, within that node's cut if it has one; and it isn't past its limit - (Users), by the limit that holds. A `retire`, a stop and an `unvouch` are never - outside a cut they set themselves, nor left out with their carrier. A user is - **out** where it counts through no `create` or `vouch` any more, or where it gave - itself up. It is **gone** once seen out for `gone`, or where a decision freed its - name; and gone it stays, whatever is vouched or cut off after. What stopped - counting for good (Cuts) counts no more, whatever comes after. + change holds, by the creation of its root that remains over all the changes, its + creations ordered by the other roots' nodes alone, and none while two contest; or + given by a decision); it is within every cut set for that key (by a `retire` that + counts, or a decision); a node committed it, within that node's cut if it has one; + and it isn't past its limit (Users), by the limit that holds. A `retire`, a stop + and an `unvouch` are never outside a cut they set themselves, nor left out with + their carrier. A user is **out** where it counts through no `create` or `vouch` any + more, or where it gave itself up. It is **gone** once seen out for `gone`, or where + a decision freed its name; and gone it stays, whatever is vouched or cut off after. + What stopped counting for good (Cuts) counts no more, whatever comes after. 3. **Users' names.** A creation stands while it counts, isn't released, its user isn't gone, and a rule of the kind `user` lets its signer; a user's claim of its own name stands with it, and on where the creation doesn't. Of what stands for a name: the one that remains (Two claims, as in step 4) has the name, or has it wait while it - is out. Of a root's creations giving keys to a user the root change holds, the one - that remains gives them (read in step 2, where each statement was signed): while - they contest, the user signs nothing new, and what it signed with keys one gave - stays. + is out. Of the creations its root signed for a user the root change holds, the one + that remains gives its keys (read in step 2). 4. **Names.** A claim stands the same way, where a rule of the policy that holds lets its user: anyone who isn't gone where the rule says `"*"`, a root where it says `"{root}"`, else the user that has the name the rule gives; and a name the voters @@ -1539,8 +1548,8 @@ name), and answers from it: created it and who vouches for it; or that it is contested, between whom; or out, since where, and how long its names still wait; or gone. Also what is in the open: which root's node keeps it in past an unvouch or a cut by a witness the signer's own - nodes didn't make, and, for a user the root change holds, which roots' creations - contest its first keys. + nodes didn't make, and, for a user the root change holds, whether its root's + creations contest its first keys. * `GET /registry/claims/<kind>/<name>`: the holder, and whether the claim is settled, and final; held "while a release, a cut, or statements past a limit stand" where it was made in sight of a claim that one could bring back, and isn't final; or @@ -2119,10 +2128,10 @@ Statements and users: | 4 | Offers a statement again; or an envelope signed for another swarm, epoch, path or user ID | Nothing where it is there under its digest; refuse elsewhere | 3 | unit, exists for swarm and path: `what_an_envelope_must_be`; `signed_for_its_user_id_and_epoch` | | 5 | Commits a statement a second time, in a change with other dependencies, to move it | A statement is where it says its signer was (`seen`), whoever carries it and how often: nothing moves | 2 | unit: `a_statement_carried_twice` | | 6 | Creates a user listing a victim's public key beside its own | The victim's envelopes name the victim's ID: they count for no other | 3 | unit: `a_key_in_two_creations` | -| 7 | A second root signs a `create`, with keys of its own, for a user the root change holds, saying it saw nothing of the first | Refuse where the user has keys. Out of sight the two are ordered as claims are: each root's node saw its own first, so the two contest and neither gives keys, until the voters give first keys | 3 | unit: `first_keys_by_claim_order` | -| 8 | A root releases the `create` that gave a moved-in user its first keys, after the user signed with them, and gives it keys of its own | Refuse: no root releases its `create` for such a user; once one gives keys, they are the user's. Two roots' creates contest until the voters give first keys | 3, 5 | unit: `a_root_keeps_to_its_create` | -| 9 | A root makes its own `create` for a moved-in user contested by a twin on old dependencies, or signs a release on old dependencies once it is final, then gives the user keys of its own | Refuse: no root releases its `create`. The twin contests, in the open, until the voters give first keys; what the user signed with its keys stays | 3, 5 | unit: `a_root_keeps_to_its_create` | -| 10 | A root's twin `create` for a moved-in user, on old dependencies, to have everything the user signed with its first keys stop counting | A moved-in user's keys are read where each statement was signed, the roots' creations ordered first by the roots' nodes alone: the twin freezes the user until the voters say, and takes nothing back | 3, 5 | unit: `first_keys_are_read_where_signed` | +| 7 | A root other than the one the root change names for a moved-in user signs a `create` for it, with keys of its own, saying it saw nothing of the first | Refuse: only the root named gives a moved-in user its keys | 3 | unit: `first_keys_by_the_named_root` | +| 8 | A root releases the `create` that gave a moved-in user its first keys, after the user signed with them, and gives it keys of its own | Refuse: no root releases its `create` for such a user; once one gives keys, they are the user's | 3, 5 | unit: `a_root_keeps_to_its_create` | +| 9 | The root named for a moved-in user makes its own `create` contested by a twin on old dependencies, or signs a release on old dependencies once it is final, then gives the user keys of its own | Refuse the release. The twin is late for good where another root's node had the first standing and not the twin; else the two contest, in the open, nothing signed with the keys of either counting, until the voters give first keys: what was signed with the keys they give counts then | 3, 5; not promised | unit: `a_root_keeps_to_its_create`, `a_twin_create_is_late` | +| 10 | With the keys of a twin `create` on old dependencies, signs as a moved-in user (hosts, claims, `node` statements, vouches), each in a change whose history holds the twin and not the first | A moved-in user's keys are those of its root's creation that remains over all the changes, not where each statement was signed: a twin late for good gives keys nowhere, and two that contest give none until the voters say | 3 | unit: `first_keys_by_the_creation_that_remains` | | 11 | Users vouch for each other in a ring away from the roots; a user vouches for its creator | None is vouched for by it | 3 | unit, resolve: `no_line_no_user` | | 12 | Creates a name in sight of its creation | Refuse | 4 | unit: `a_name_created_once` | | 13 | Commits a user's claim on old dependencies, or holds it back, as a node of another party the user claimed through | Who commits a statement says nothing of it: what its signer saw is in its signature, and a claim committed late is late. A user's own claims of one name are one, from whatever node | 4 | unit: `a_claim_through_any_node` | @@ -2319,9 +2328,10 @@ the first voters, with their keys and nodes; and for each namespace of the repos a user without keys, its hosts as they are, plain, and their addresses as claims in its name. The genesis change is trusted as it is (every party is given its hash), so what it holds counts without signatures: a host it holds counts until its user signs -over it, and a claim it holds is its user's. One of the roots gives each user its -first keys as it comes; from then on the user signs its own, and votes once a decision -lists it. A namespace whose user never comes stays as the genesis change has it. +over it, and a claim it holds is its user's. The root the genesis change names for +each user gives it its first keys as it comes; from then on the user signs its own, +and votes once a decision lists it. A namespace whose user never comes stays as the +genesis change has it. What to weigh, moving in. With one maintainer as the only root and voter, that one settles every claim, decides alone, and sees alone what a third of the voters see, |
