docs: federation: lines, time from the stamps, the last decision holds

What the maintainer asked of the design, and what it changed:

* Lines. A user is in while it has a line: a chain of creations and
  vouches from the root. When its creator goes, one that another
  vouched for stays without doing anything. The witnesses of its
  claims are the users on the lines it stands on: its creation's, and
  those of vouches it accepted (`accept`), so nobody gets a say about
  a user's names by vouching for it unasked. Why only its signer
  takes a vouch back is said where unvouching is.
* Lengths of time are read between two stamps of one node, with what
  that node had seen at each: a voter is absent once a third of the
  voters saw it silent for long, a user gone once they saw it out. No
  clock is set against another, and why a third.
* Decisions. A proposal is decided as soon as the nodes of two thirds
  of the voters hold its votes: at once, not at the end of a window.
  Any number are open at a time, within a limit a voter. Of the
  decisions of one matter the last holds, by which proposal was made
  in sight of which, so two decided at once stop nothing. A remake's
  base is named by its coordinator, a node of the proposer.
* The policy changes by a decision, as a whole, with no remake: a
  remake throws history away and does nothing else. What a policy no
  longer covers doesn't count, and a remake keeps it aside for an
  epoch or drops it, as the policy says. Going apart by a fork stays
  for those a decision leaves behind.
* What a remake leaves out, so that the document's size goes by what
  stands: a release is a statement in its epoch, the remake deletes.
* Names are written as they are used, in the document and in the
  rules alike, and compared by their segments: structure, not
  meaning. A rule may leave a name to the voters to give.
* Who vouched for whom changes nothing in who connects to whom: a
  node keeps its seeds and its user's other nodes as neighbours.

The attacks are 83, the stages fifteen.

future-work.md: guides to write (keys, the root, starting a swarm,
voting, a registry), policies merged.

0 files changed, 0 insertions, 0 deletions