aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/proposing-and-voting.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-18 12:48:29 +0000
committertv <tv@krebsco.de>2026-11-18 13:59:42 +0100
commitd130c0612b4c63f2d30da65ebcc231018c1f2606 (patch)
tree8700f2d53351cbbecbe772ea7701bf6240d5210c /docs/guides/federation/proposing-and-voting.md
parent0bfe07af92a775b0e896e0fc5a989a1d9b65f7b3 (diff)
docs: references to another document's section linked to it
Where a document names a section of another after linking to it ("([`store.md`](store.md), Pinned checkpoints)"), the name links to that section too, by the id both GitHub and cgit's about filter give its heading; paragraphs that grew past the width are wrapped anew, links and code kept on one line each.
Diffstat (limited to 'docs/guides/federation/proposing-and-voting.md')
-rw-r--r--docs/guides/federation/proposing-and-voting.md19
1 files changed, 11 insertions, 8 deletions
diff --git a/docs/guides/federation/proposing-and-voting.md b/docs/guides/federation/proposing-and-voting.md
index 91da019..e656083 100644
--- a/docs/guides/federation/proposing-and-voting.md
+++ b/docs/guides/federation/proposing-and-voting.md
@@ -3,8 +3,9 @@
Everything a federation decides is a change of its policy: who the parties are, the keys
they vote with, who writes where, a checkpoint. A party proposes a version, the parties
vote, and once two thirds of them back it, it is written. The rules are the design's
-([`federation.md`](../../federation.md), The policy, Changing the policy). A party's
-node list and its key set are its own to write, without a vote
+([`federation.md`](../../federation.md), [The policy](../../federation.md#the-policy),
+[Changing the policy](../../federation.md#changing-the-policy)). A party's node list and
+its key set are its own to write, without a vote
([`common-changes.md`](common-changes.md#what-a-party-does-by-itself)).
## Writing a version
@@ -31,7 +32,8 @@ for the changes made most):
version names for it: a party adds and takes off its nodes by itself
([`common-changes.md`](common-changes.md#what-a-party-does-by-itself)).
* **`rules`**: in order, the first matching a path deciding who writes there
- ([`writing-and-reading.md`](writing-and-reading.md), Places).
+ ([`writing-and-reading.md`](writing-and-reading.md),
+ [Places](writing-and-reading.md#places)).
* **`checkpoint`**, only where the version moves the store to a checkpoint: the heads.
Otherwise leave it out, though the current version names one: its heads are behind,
and a version naming them again is never written.
@@ -87,10 +89,10 @@ record before it sends the vote. It casts no vote that would make its party vote
party backed is dead. The client fetches the votes that made it so from the node, and
keeps them in the record beside the new `true`.
-A party votes from one client, with one record: two clients backing two proposals at
-once is voting twice, and shows ([`federation.md`](../../federation.md), Changing the
-policy). A party whose node votes for it by itself votes by hand only through that
-node, which keeps its one record:
+A party votes from one client, with one record: two clients backing two proposals at once
+is voting twice, and shows ([`federation.md`](../../federation.md),
+[Changing the policy](../../federation.md#changing-the-policy)). A party whose node votes
+for it by itself votes by hand only through that node, which keeps its one record:
```sh
continuum-party --node http://tv:secret@localhost:3000 vote 8d02… yes --through
@@ -152,7 +154,8 @@ continuum-party --node http://tv:secret@localhost:3000 proposals
```
A node's dashboard shows them so too, and where the node votes for its party by itself,
-votes through it ([`dashboard.md`](../../dashboard.md), Federation).
+votes through it ([`dashboard.md`](../../dashboard.md),
+[Federation](../../dashboard.md#federation)).
`GET /events/{id}` shows a proposing event, the version it proposes in `proposal`, and
a vote, signed by its party. A node lacking some votes reads a proposal as neither passed