diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/federation.md | 4 | ||||
| -rw-r--r-- | docs/guides/federation/forking-and-following.md | 7 | ||||
| -rw-r--r-- | docs/guides/federation/proposing-and-voting.md | 8 | ||||
| -rw-r--r-- | docs/openapi.yaml | 10 |
4 files changed, 22 insertions, 7 deletions
diff --git a/docs/federation.md b/docs/federation.md index e47da93..f0099ef 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -626,7 +626,8 @@ store of its own from the federation's ([`store.md`](store.md), [Forks](store.md 3. The others join it as a node joins any swarm, by its ID. A node holding the history up to those heads builds the root and checks it, says what it holds that those heads lack, what the fork's version changes of the one current there, its rules and their - order among it, and, party by party, whether it gives the party the keys it had there: + order among it, the places holding a value whose writer it changes, and, party by + party, whether it gives the party the keys it had there: a founder may give a party that didn't go keys of its own. A node that doesn't hold that history takes the root on its operator's word, as its operator names the fork. @@ -783,6 +784,7 @@ fold, with crafted events. *Sim*: a simulation. *Bench*: measured, not judged. | 69 | A key a version names, stolen, writes its party's node list at a history from before the version naming the party's keys anew, beside the list the party writes under that version, several, for the lowest ID | The party's counts: of a party's lists, those written under the latest version come first | unit | | 70 | A checkpoint's version proposed again, by an event beside its heads | Voters back it all the same, as a proposal lapses with the move, and vote on the events proposing it above its heads, as a node shows them; a version event on votes beside them is refused | unit | | 71 | Merge events under the base revision, signed by a node its party doesn't list, by a party's key, or spelled otherwise | Refused, or none: a merge event is taken only under a revision with merge events, signed by a node its party's node list names, its `merge` `true`; it counts for nothing | unit | +| 72 | A version, or a fork's, admitting a party named as a segment of places others write, or changing the rules or their order, so that who writes those places moves, rules unchanged in the first case | Taken, as any version two thirds pass, or any fork: a party's client names each place holding a value whose writer a proposal changes before it is voted on, and a fork's check does for the fork's version | unit | ## Roads not taken diff --git a/docs/guides/federation/forking-and-following.md b/docs/guides/federation/forking-and-following.md index dafa974..4890a61 100644 --- a/docs/guides/federation/forking-and-following.md +++ b/docs/guides/federation/forking-and-following.md @@ -57,16 +57,19 @@ continuum-party --node http://lass:secret@localhost:3000 check fork-root # its heads lack 0c7e… # its version changes: # changes: "3a90…" -> "b41f…" +# keys.euer: {"keys":["ssh-ed25519 AAAA…"],"since":0} -> - # keys.makefu: {"keys":["ssh-ed25519 AAAA…"],"since":2} -> {"keys":[…],"since":5} -# nodes.lass: {"nodes":["continuum:9c07…"],"since":0} -> {…,"since":5} +# nodes.euer: {"nodes":["continuum:3b1e…"],"since":0} -> - # number: 4 -> 5 +# who writes home/euer/hosts/x: euer -> nobody # makefu's keys: ["ssh-ed25519 AAAA…"] here, ["ssh-ed25519 AAAA…"] in the fork ``` Whether it builds that root at those heads; what it took that the heads lack (neither among them, in their history, nor above them), which the fork doesn't hold; what the fork's version changes of the one current at those heads, field by field, its rules and -their order among them, which say who writes where; and, party by party, the keys the +their order among them, which say who writes where, and the places holding a value whose +writer it changes; and, party by party, the keys the fork's version gives otherwise than the party had at those heads. A node that doesn't hold that history takes the root on its operator's word, who names the fork by its ID: compare that ID whole, as a founder trying versions can steer its first few digits. diff --git a/docs/guides/federation/proposing-and-voting.md b/docs/guides/federation/proposing-and-voting.md index 330d670..f052276 100644 --- a/docs/guides/federation/proposing-and-voting.md +++ b/docs/guides/federation/proposing-and-voting.md @@ -157,8 +157,12 @@ curl -s -u tv:secret localhost:3000/events/counts | jq .proposals # "proposals":["c41e…"],"votes":["5a77…","e019…"],"yes":["tv"]}} ``` -The client shows the same, why it backs one not, by the federation it knows, and what -each proposal's version changes of the current one, field by field and party by party: +The client shows the same, why it backs one not, by the federation it knows, what each +proposal's version changes of the current one, field by field and party by party, and +the places holding a value whose writer it changes (`who writes names/wiki/a: tv -> +wiki`): admitting a party named as a segment of a place is, or changing the rules or +their order, moves who writes there, rules unchanged in the first case, and what was +written there counts no more once it passes: ```sh continuum-party --node http://tv:secret@localhost:3000 proposals diff --git a/docs/openapi.yaml b/docs/openapi.yaml index 6cef2f2..b5e7b14 100644 --- a/docs/openapi.yaml +++ b/docs/openapi.yaml @@ -1696,7 +1696,9 @@ paths: events it took that are neither among them, nor in their history, nor above them); what the fork's version changes of the version current at those heads, a line each as `field: before -> after`, its rules among them, `keys` and `nodes` - party by party (`changes`); and the parties whose keys the fork's version gives + party by party (`changes`); of the places holding a value there, those whose + writer the fork's version changes, as `place: before -> after`, `nobody` where no + rule gives it one (`writers`); and the parties whose keys the fork's version gives otherwise than they had at those heads, each with its keys there and in the fork. A node that doesn't hold that history takes a fork's root on its operator's word, who names @@ -1715,7 +1717,7 @@ paths: application/json: schema: type: object - required: [fork, builds, why, lacking, changes, keys] + required: [fork, builds, why, lacking, changes, writers, keys] properties: fork: type: string @@ -1732,6 +1734,10 @@ paths: type: array items: type: string + writers: + type: array + items: + type: string keys: type: object additionalProperties: |
