diff options
Diffstat (limited to 'docs/federation.md')
| -rw-r--r-- | docs/federation.md | 50 |
1 files changed, 29 insertions, 21 deletions
diff --git a/docs/federation.md b/docs/federation.md index 6269203..9dc4035 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -293,10 +293,10 @@ grows. A statement is signed by one user and says one thing: to carry it, is a statement's place wherever its place matters: carried a second time, by anyone, it is where it was. Its envelope names the register as its path. * **A user is its creation.** The `create` statement's digest is the **user ID**, and - every envelope the user signs names it, with the name, the swarm and the epoch it - was signed in. Two creations of one name are two users with two sets of keys; which - has the name is decided below, and a key listed in both signs for the one its - envelope names. + every envelope the user signs names it, with the swarm and the epoch it was signed + in. Two creations of one name are two users with two sets of keys; which has the + name is decided below, and a key listed in both signs for the one its envelope + names. * **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 @@ -1316,7 +1316,8 @@ follows every decision. Its operator has it refuse: What refusing does: * **Before.** While a proposal's votes run, a node whose bounds it breaks says so in - its member entry, so the voters see who would go (`GET /registry/decisions`). + its member entry (`refuses`), so the voters see who would go + (`GET /registry/decisions`). * **The epoch without it.** A node that refuses a decision moves to the epoch built where its proposal was signed (at the changes the proposal says its signer saw, which no honest node took it up without holding all it had held `window` @@ -1354,33 +1355,39 @@ saying so (Continuum changing under a swarm). Names of fields are the design's, encoding the first stage's. **Every envelope** (a statement): `swarm` (the swarm's ID), `epoch` (the epoch it is -signed in), `path` (its register, under its own digest), `kind`, `user` and `userId` -(its signer: the name it had when it signed, and the ID; a `create`'s signer is the -creator), `seen` (the hashes of the changes its signer had seen), `number` (the -number of its kind among its user's statements: Users), `key` (the public key that -signs) and the signature, over all the rest. Beside those, by kind: +signed in), `path` (its register, under its own digest), `kind`, `userId` (its +signer's ID; a `create`'s signer is the creator), `seen` (the hashes of the changes +its signer had seen), `number` (the number of its kind among its user's statements: +Users), `signingKey` (the public key that signs) and the signature, over all the rest. +Beside those, by kind: | Kind | Fields | |---|---| | `create` | `name`, `keys` (the first keys, public); a root's, for a user the root change holds: `for`, its ID there | | `vouch` | `for`, the ID of the user vouched for | -| `unvouch` | `of`, the digest of the `create` or `vouch` taken back | -| `key` | `key`, the key added (the signing key is above it) | -| `retire` | `key`, the key retired; `cut`, change hashes; `keeps`, the digests it keeps within the cut (Cuts) | +| `unvouch` | `of`, the digest of the `create` or `vouch` taken back; or `for`, the ID of a user the root change holds without a creator, which the roots take back together | +| `key` | `added`, the key added (the signing key is above it) | +| `retire` | `retired`, the key retired; `cut`, change hashes; `keeps`, the digests it keeps (Cuts) | | `node` | `node`, the node's ID; a stop: `stop`, with `cut` and `keeps` | -| `release` | `of`, the digest of the claim, vote or proposal given up; or `self`, the user giving itself up (signed with a first key) | +| `release` | `of`, the digest of the claim, vote or proposal given up; or `claimKind` and `name`, a name a decision gave or made over; or `self`, the user giving itself up (signed with a first key) | | `claim` | `claimKind` and `name` | | `propose` | `matter`, `holds` (below), `matterNumber` (its number among its matter's proposals: Decisions) | | `vote` | `proposal`, its digest; `ends`, when it runs out | +**A value's envelope**: `swarm`, `epoch`, `path` (its place), `userId`, `signingKey`, +`prev` (the digest of a value that counts at its place where it is signed, or none), +the value (or `null`, putting nothing there), and the signature. It says nothing of +what its signer saw: where a value was signed, wherever a rule asks, is the change +that carries it. + A proposal's `matter` and what it `holds`: | Matter | `holds` | |---|---| | `number`, naming it | the value | | `policy` | the rest of the policy, whole | -| `firstKeys`, naming the user | the keys, and a `cut` for those it has | -| `name`, naming an out user and the name | free, or the user ID it is given to | +| `firstKeys`, naming the user | the keys, and a `cut` with its `keeps` for those it has | +| `name`, naming an out user, a kind and a name | free, or the user ID it is given to | | `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 | @@ -1403,9 +1410,10 @@ is: the base). * **A member entry**, of the shape its policy's version gives it, within `limits.entry`: what it is today (its addresses, what it reaches, whether it is - ready, its alive stamp), and `writersFor` (the user its writers count for: Users) - and `digest` (the registry as it resolves at the change's dependencies: Continuum - changing under a swarm). + ready, its alive stamp), `writersFor` (the user its writers count for: Users), + `refuses` (the open proposals whose decision its bounds would refuse: Refusing a + decision) and `digest` (the registry as it resolves at the change's dependencies: + Continuum changing under a swarm). ### What every node judges @@ -1437,7 +1445,7 @@ A change is valid if, in the document at its dependencies: within `limits.entry`), its own records of proposals, its carry record, and what it writes of a remake as in every swarm (its ack; a coordinator's proposal and decision, of the kind `compact`), it writes only envelopes, each naming the swarm, - its epoch, its path, its user and user ID, and for a statement what its signer saw + its epoch, its path and its user's ID, and for a statement what its signer saw (`seen`, changes in this change's history) and, where statements of its kind are numbered, the number that gives it, signed with a key that is that user's there and not retired there. Any node commits it, but a `node` statement, which the node it @@ -1742,7 +1750,7 @@ key that step 2 gives its user for the change that carries it. A key is a user's by statements signed with keys above it, up to its creation, signed by its creator, and so on up to a root, in the root every node was given; or by a decision, which is promise 7's. A node that carries doesn't sign in the user's place: the envelope names -its swarm, epoch, path, user and user ID *(checked for swarm, path and user: +its swarm, epoch, path and user ID *(checked for swarm, path and the user's name: `access::envelope::check`)*, so it counts nowhere else and for nobody else. A name is held by a claim so signed, by a rule, or by a decision. Across a remake: every node builds the snapshot from changes it judged, so the snapshot holds only what counted or |
