From d130c0612b4c63f2d30da65ebcc231018c1f2606 Mon Sep 17 00:00:00 2001 From: tv Date: Wed, 18 Nov 2026 12:48:29 +0000 Subject: 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. --- docs/guides/federation/building-on-the-api.md | 14 +++++++++----- docs/guides/federation/checkpoints.md | 17 +++++++++-------- docs/guides/federation/common-changes.md | 10 ++++++---- docs/guides/federation/designing-rules.md | 3 ++- docs/guides/federation/forking-and-following.md | 5 +++-- docs/guides/federation/getting-started.md | 5 +++-- docs/guides/federation/keys.md | 7 ++++--- docs/guides/federation/promises.md | 7 +++++-- docs/guides/federation/proposing-and-voting.md | 19 +++++++++++-------- docs/guides/federation/refusals-and-drops.md | 11 +++++++---- docs/guides/federation/remakes.md | 7 ++++--- docs/guides/federation/running-a-node.md | 10 +++++----- docs/guides/federation/upgrades.md | 14 +++++++------- docs/guides/federation/voting-by-itself.md | 18 +++++++++--------- docs/guides/federation/watching.md | 11 ++++++----- docs/guides/federation/when-things-go-wrong.md | 12 +++++++----- docs/guides/federation/writing-and-reading.md | 7 ++++--- 17 files changed, 101 insertions(+), 76 deletions(-) (limited to 'docs/guides') diff --git a/docs/guides/federation/building-on-the-api.md b/docs/guides/federation/building-on-the-api.md index 4f37b91..45394ed 100644 --- a/docs/guides/federation/building-on-the-api.md +++ b/docs/guides/federation/building-on-the-api.md @@ -2,14 +2,17 @@ An application on a federated swarm reads what counts at a node and writes as a party. This guide says how, through the client or with code of its own. The formats are the -design's ([`federation.md`](../../federation.md), Events, The policy, What counts). +design's ([`federation.md`](../../federation.md), [Events](../../federation.md#events), +[The policy](../../federation.md#the-policy), +[What counts](../../federation.md#what-counts)). ## Reading `GET /events/counts` is what counts, as the node reads it now: the values at places (`values`), the current version and its rules, each party's keys and nodes, the members -([`writing-and-reading.md`](writing-and-reading.md), Reading). There is no stream of what -counts: read it again when the store's heads change (`heads` in `GET /events`). +([`writing-and-reading.md`](writing-and-reading.md), +[Reading](writing-and-reading.md#reading)). There is no stream of what counts: read it +again when the store's heads change (`heads` in `GET /events`). What a node answers is its word: it may be behind, and an application that must not take it on trust reads the events themselves (`GET /events/{id}`) and checks their signatures, @@ -25,8 +28,9 @@ continuum-party --node http://tv:secret@localhost:3000 --key laptop.key \ ``` It signs on the heads the node shows, records what it signed, and puts it; `again` signs -anew what a move to a checkpoint refused ([`writing-and-reading.md`](writing-and-reading.md), -After a move). +anew what a move to a checkpoint refused +([`writing-and-reading.md`](writing-and-reading.md), +[After a move](writing-and-reading.md#after-a-move)). ## Writing with code of its own diff --git a/docs/guides/federation/checkpoints.md b/docs/guides/federation/checkpoints.md index 23f0e9c..66f79e9 100644 --- a/docs/guides/federation/checkpoints.md +++ b/docs/guides/federation/checkpoints.md @@ -2,8 +2,8 @@ A checkpoint writes down what counts at some heads, so that nodes forget the rest and hold what is relevant. The parties pass it as any version. The rules are the design's -([`federation.md`](../../federation.md), Checkpoints; [`store.md`](../../store.md), -Checkpoints). +([`federation.md`](../../federation.md), [Checkpoints](../../federation.md#checkpoints); +[`store.md`](../../store.md), [Checkpoints](../../store.md#checkpoints)). ## What one does @@ -23,12 +23,13 @@ isn't above the heads, which its party signs again ([After a move](#after-a-move A version that only moves the store on is the current one with the next `number`, the current version's hash as `changes`, and the heads as `checkpoint` -([`proposing-and-voting.md`](proposing-and-voting.md), Writing a version). The heads are -events after the current checkpoint, at which the current version is current too, none in +([`proposing-and-voting.md`](proposing-and-voting.md), +[Writing a version](proposing-and-voting.md#writing-a-version)). The heads are events +after the current checkpoint, at which the current version is current too, none in another's history, their IDs ascending: heads a node showed (`heads` in `GET /events`) -once the version was written, and that it has held for a while since, so that every -node holds them. Propose it afterwards: the client signs the proposal on the heads its -node shows then, above the ones it names, as it must be. +once the version was written, and that it has held for a while since, so that every node +holds them. Propose it afterwards: the client signs the proposal on the heads its node +shows then, above the ones it names, as it must be. Like any version, it lapses the proposals on the version before: propose one where nothing that can still pass is proposed on the current version. @@ -75,4 +76,4 @@ leaves out what a checkpoint forgot, the document holds what came before, and a that was away builds the checkpoint from it as any. After such a remake, a node away across it, or joining, takes the checkpoint only where its operator pins it: ask a node you trust for it (`checkpoint` in `GET /events`) -([`running-a-node.md`](running-a-node.md), Joining). +([`running-a-node.md`](running-a-node.md), [Joining](running-a-node.md#joining)). diff --git a/docs/guides/federation/common-changes.md b/docs/guides/federation/common-changes.md index 1dd30c1..a18d863 100644 --- a/docs/guides/federation/common-changes.md +++ b/docs/guides/federation/common-changes.md @@ -1,9 +1,10 @@ # Common changes Recipes for the changes a federation makes most, each a version to propose and vote on -([`proposing-and-voting.md`](proposing-and-voting.md)), and a few a party makes by -itself. The rules are the design's ([`federation.md`](../../federation.md), The policy, -Keys, Nodes). +([`proposing-and-voting.md`](proposing-and-voting.md)), and a few a party makes by itself. +The rules are the design's ([`federation.md`](../../federation.md), +[The policy](../../federation.md#the-policy), [Keys](../../federation.md#keys), +[Nodes](../../federation.md#nodes)). ## The next version @@ -29,7 +30,8 @@ jq --arg key "$(cut -d' ' -f1,2 makefu.key.pub)" --arg node continuum:e2a8… ' A party let in without nodes has an empty list (`nodes: []`) and writes through any node that takes its events. It begins its record before it votes: from the root, as it never -voted ([`proposing-and-voting.md`](proposing-and-voting.md), Voting). +voted ([`proposing-and-voting.md`](proposing-and-voting.md), +[Voting](proposing-and-voting.md#voting)). ## Taking a party out diff --git a/docs/guides/federation/designing-rules.md b/docs/guides/federation/designing-rules.md index 82cec96..db61f62 100644 --- a/docs/guides/federation/designing-rules.md +++ b/docs/guides/federation/designing-rules.md @@ -2,7 +2,8 @@ The rules of a version say who writes where. Good rules let routine work go without a vote and leave votes for what is nobody's by its spelling. The rules are the design's -([`federation.md`](../../federation.md), The policy, Shared identifiers). +([`federation.md`](../../federation.md), [The policy](../../federation.md#the-policy), +[Shared identifiers](../../federation.md#shared-identifiers)). ## How they match diff --git a/docs/guides/federation/forking-and-following.md b/docs/guides/federation/forking-and-following.md index 51d56ab..ffc4fae 100644 --- a/docs/guides/federation/forking-and-following.md +++ b/docs/guides/federation/forking-and-following.md @@ -2,8 +2,9 @@ Any group can carry on without the rest, by a fork: a store of its own, whose root is a checkpoint at heads of the federation's. It needs nobody's vote and binds only those who -go. The rules are the design's ([`federation.md`](../../federation.md), Forks; -[`store.md`](../../store.md), Forks). +go. The rules are the design's ([`federation.md`](../../federation.md), +[Forks](../../federation.md#forks); [`store.md`](../../store.md), +[Forks](../../store.md#forks)). ## When diff --git a/docs/guides/federation/getting-started.md b/docs/guides/federation/getting-started.md index 5dcff5b..003d56e 100644 --- a/docs/guides/federation/getting-started.md +++ b/docs/guides/federation/getting-started.md @@ -20,7 +20,7 @@ That builds the node, `continuum`, and the party's client, `continuum-party`, in The version names each party's keys, and the party signs with them. A key is `ssh-ed25519` or `ecdsa-sha2-nistp256`. The client reads an OpenSSH private key file without a passphrase, of an Ed25519 key, or signs through an ssh-agent holding the key -([`keys.md`](keys.md), Keys in an ssh-agent): +([`keys.md`](keys.md), [Keys in an ssh-agent](keys.md#keys-in-an-ssh-agent)): ```sh ssh-keygen -t ed25519 -N '' -f tv.key @@ -119,7 +119,8 @@ continuum-party --node http://tv:secret@localhost:3000 --key tv.key --record tv. ``` The value is JSON. The client's options can go in a configuration file instead, as the -node's do ([`configuration.md`](../../configuration.md), The party's client): +node's do ([`configuration.md`](../../configuration.md), +[The party's client](../../configuration.md#the-partys-client)): `continuum-party --config tv.toml write …`. lass reads it on its node, with everything else that counts: diff --git a/docs/guides/federation/keys.md b/docs/guides/federation/keys.md index 7f5bd7a..add7cb3 100644 --- a/docs/guides/federation/keys.md +++ b/docs/guides/federation/keys.md @@ -1,8 +1,9 @@ # Keys A party has two kinds of keys: those its version names, and those of its key set. The -rules are the design's ([`federation.md`](../../federation.md), Keys); this guide says -how to keep them, change them, and what to do when one is stolen. +rules are the design's ([`federation.md`](../../federation.md), +[Keys](../../federation.md#keys)); this guide says how to keep them, change them, and what +to do when one is stolen. ## The two kinds @@ -115,4 +116,4 @@ set that party wrote count no more. A node's own key (`--node-key-file`) is no party's: it is the node, the node ID its party lists. A stolen node key is a node the party takes off its list -([`running-a-node.md`](running-a-node.md), Who syncs). +([`running-a-node.md`](running-a-node.md), [Who syncs](running-a-node.md#who-syncs)). diff --git a/docs/guides/federation/promises.md b/docs/guides/federation/promises.md index 3c9a257..9a1b92f 100644 --- a/docs/guides/federation/promises.md +++ b/docs/guides/federation/promises.md @@ -3,7 +3,9 @@ A federated swarm is kept by parties that don't trust each other. This guide says, in plain words, what holds whatever any of them does, what doesn't, and what that asks of a party, an operator and an application. The design says it precisely -([`federation.md`](../../federation.md), Parties and the adversary, What is promised). +([`federation.md`](../../federation.md), +[Parties and the adversary](../../federation.md#parties-and-the-adversary), +[What is promised](../../federation.md#what-is-promised)). ## Who is who @@ -58,4 +60,5 @@ to whom. A party whose machine is taken over whole is the adversary from then on trust, and keep its store file ([`running-a-node.md`](running-a-node.md)). * **An application**: read from a node you trust, as what it answers is its word; check the events yourself where that matters - ([`writing-and-reading.md`](writing-and-reading.md), Reading). + ([`writing-and-reading.md`](writing-and-reading.md), + [Reading](writing-and-reading.md#reading)). 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 diff --git a/docs/guides/federation/refusals-and-drops.md b/docs/guides/federation/refusals-and-drops.md index 09b0442..c4566e3 100644 --- a/docs/guides/federation/refusals-and-drops.md +++ b/docs/guides/federation/refusals-and-drops.md @@ -1,8 +1,10 @@ # Refusals and drops What a node refuses, what of that is its own, and how its operator has it drop what it -took and take it back. The rules are the store's ([`store.md`](../../store.md), A node's -own) and the federation's ([`federation.md`](../../federation.md), Changing the policy). +took and take it back. The rules are the store's ([`store.md`](../../store.md), +[A node's own](../../store.md#a-nodes-own)) and the federation's +([`federation.md`](../../federation.md), +[Changing the policy](../../federation.md#changing-the-policy)). ## What a node refuses @@ -67,5 +69,6 @@ as it reads its document again. It answers `204`. ## When to Dropping and taking back are how an operator chooses a side where keys voted twice -([`when-things-go-wrong.md`](when-things-go-wrong.md), Choosing a side), or keeps out an -event it won't hold: whatever it drops, it reads no more, while the others may. +([`when-things-go-wrong.md`](when-things-go-wrong.md), +[Choosing a side](when-things-go-wrong.md#choosing-a-side)), or keeps out an event it +won't hold: whatever it drops, it reads no more, while the others may. diff --git a/docs/guides/federation/remakes.md b/docs/guides/federation/remakes.md index ef60266..05c27ab 100644 --- a/docs/guides/federation/remakes.md +++ b/docs/guides/federation/remakes.md @@ -3,7 +3,8 @@ A remake moves a swarm to a new document, for Automerge's sake only: the store needs none, and its events stay what they are. A federated swarm takes compactions only. How a remake runs is as in any swarm ([`remakes.md`](../../remakes.md)); this guide says what is -otherwise. The rules are the store's ([`store.md`](../../store.md), Remakes). +otherwise. The rules are the store's ([`store.md`](../../store.md), +[Remakes](../../store.md#remakes)). ## Proposing one @@ -53,8 +54,8 @@ document, one its operator pins (`--store-checkpoint`), or, to an empty document root; and only one with its swarm's policy. A made-up epoch can withhold events from a node and keep it apart from the others, but make it take nothing it wouldn't. A node that can't follow the others' epoch, as its snapshot holds a checkpoint it can't build, -follows it once its operator pins that checkpoint -([`checkpoints.md`](checkpoints.md), Nodes that weren't there). +follows it once its operator pins that checkpoint ([`checkpoints.md`](checkpoints.md), +[Nodes that weren't there](checkpoints.md#nodes-that-werent-there)). ## Without remakes diff --git a/docs/guides/federation/running-a-node.md b/docs/guides/federation/running-a-node.md index b303fab..5d881d6 100644 --- a/docs/guides/federation/running-a-node.md +++ b/docs/guides/federation/running-a-node.md @@ -36,11 +36,11 @@ node refuses to start with them. ## Its files -Beside those of every node ([`lifecycle.md`](../../lifecycle.md), What the files are -for), the store file. Back up the node key, as every node's: its node ID is what its -party lists, and a new key is a new node, which the party lists anew. The document file -and the store file go together: the store file says what the node refuses of what the -document holds. +Beside those of every node ([`lifecycle.md`](../../lifecycle.md), +[What the files are for](../../lifecycle.md#what-the-files-are-for)), the store file. Back +up the node key, as every node's: its node ID is what its party lists, and a new key is a +new node, which the party lists anew. The document file and the store file go together: +the store file says what the node refuses of what the document holds. ## Who syncs diff --git a/docs/guides/federation/upgrades.md b/docs/guides/federation/upgrades.md index 95dab12..570de19 100644 --- a/docs/guides/federation/upgrades.md +++ b/docs/guides/federation/upgrades.md @@ -1,17 +1,17 @@ # Upgrades and the federation's number Upgrading the continuum a federated swarm's nodes run, and what the federation's number -in each version says. The rules are the design's -([`federation.md`](../../federation.md), Changing the federation). +in each version says. The rules are the design's ([`federation.md`](../../federation.md), +[Changing the federation](../../federation.md#changing-the-federation)). ## Upgrading continuum A node of a federated swarm upgrades as any node does -([`operations.md`](../../operations.md), Upgrading): one at a time, restarted with its -files. Across a change of the wire format, upgraded nodes and the others don't talk, and -the swarm is split until all are upgraded; a remake needs the same Automerge on every -node, and one with another rejoins instead of switching. Until continuum's first release, -take every upgrade as such a change. +([`operations.md`](../../operations.md), [Upgrading](../../operations.md#upgrading)): one +at a time, restarted with its files. Across a change of the wire format, upgraded nodes +and the others don't talk, and the swarm is split until all are upgraded; a remake needs +the same Automerge on every node, and one with another rejoins instead of switching. Until +continuum's first release, take every upgrade as such a change. Nobody runs every node of a federated swarm: each party's operators upgrade its nodes. Agree on when, among the parties, and upgrade close together. diff --git a/docs/guides/federation/voting-by-itself.md b/docs/guides/federation/voting-by-itself.md index bf7a01e..300f60c 100644 --- a/docs/guides/federation/voting-by-itself.md +++ b/docs/guides/federation/voting-by-itself.md @@ -2,8 +2,8 @@ A party may have one of its nodes vote and propose for it, by rules its operator sets, written nowhere in the swarm: every node judges what such a node signs as any vote or -proposal. The rules are the design's ([`federation.md`](../../federation.md), Votes a -node casts by itself). +proposal. The rules are the design's ([`federation.md`](../../federation.md), +[Votes a node casts by itself](../../federation.md#votes-a-node-casts-by-itself)). ## Setting it up @@ -56,13 +56,13 @@ or `POST /admin/events/vote` with `{"proposal": "8d02…", "yes": true}`. ## What it keeps to What a party's client keeps to: one `true` at a time, never `true` and `false` on one -proposal, nothing on the version its record began on, and no `true` for a proposal that -is no version ([`proposing-and-voting.md`](proposing-and-voting.md), Voting). And, for a -version naming a checkpoint, the voters' rule: it backs one only where it changes nothing -of the current version but its number, what it changes and its checkpoint, and its heads -leave out nothing it held for a while before it was proposed -([`checkpoints.md`](checkpoints.md), Backing one). A vote by hand through it keeps to the -same. +proposal, nothing on the version its record began on, and no `true` for a proposal that is +no version ([`proposing-and-voting.md`](proposing-and-voting.md), +[Voting](proposing-and-voting.md#voting)). And, for a version naming a checkpoint, the +voters' rule: it backs one only where it changes nothing of the current version but its +number, what it changes and its checkpoint, and its heads leave out nothing it held for a +while before it was proposed ([`checkpoints.md`](checkpoints.md), +[Backing one](checkpoints.md#backing-one)). A vote by hand through it keeps to the same. It signs its votes on the events proposing what it votes on, and its checkpoint proposals on its heads, so that a version event may be written on them. diff --git a/docs/guides/federation/watching.md b/docs/guides/federation/watching.md index c04a6a3..f55005a 100644 --- a/docs/guides/federation/watching.md +++ b/docs/guides/federation/watching.md @@ -1,8 +1,9 @@ # What to watch What tells an operator, or a party, that a federated swarm needs them. Watch what every -node needs watching ([`operations.md`](../../operations.md), What to alert on), and -besides it, the node's store, through its API and its log. +node needs watching ([`operations.md`](../../operations.md), +[What to alert on](../../operations.md#what-to-alert-on)), and besides it, the node's +store, through its API and its log. ## Through the API @@ -10,8 +11,8 @@ besides it, the node's store, through its API and its log. twice, and nodes may be apart. Act on it at once ([`when-things-go-wrong.md`](when-things-go-wrong.md)). * **No store** (`404` from `GET /events` for longer than a start takes): the node can't - read its store ([`when-things-go-wrong.md`](when-things-go-wrong.md), A node doing less - than it should). + read its store ([`when-things-go-wrong.md`](when-things-go-wrong.md), + [A node doing less than it should](when-things-go-wrong.md#a-node-doing-less-than-it-should)). * **Proposals on the current version** (`proposals` in `GET /events/counts`): each with who voted what, and whether it passed or is dead; the party's record says what it voted. @@ -28,7 +29,7 @@ besides it, the node's store, through its API and its log. A node's dashboard (`/admin/dashboard`) shows the same in its document box, read every 5 s: the version, the parties and which of their nodes are members, the values, the proposals with who voted what and what each changes, and what the node refused -([`dashboard.md`](../../dashboard.md), Federation). +([`dashboard.md`](../../dashboard.md), [Federation](../../dashboard.md#federation)). ## In the log diff --git a/docs/guides/federation/when-things-go-wrong.md b/docs/guides/federation/when-things-go-wrong.md index de2e34a..c79f24f 100644 --- a/docs/guides/federation/when-things-go-wrong.md +++ b/docs/guides/federation/when-things-go-wrong.md @@ -2,8 +2,9 @@ What to do when a node reports a version it refused, when a party voted twice, and when a node doesn't do what it should. The rules are the design's -([`federation.md`](../../federation.md), Changing the policy; [`store.md`](../../store.md), -A node's own). +([`federation.md`](../../federation.md), +[Changing the policy](../../federation.md#changing-the-policy); +[`store.md`](../../store.md), [A node's own](../../store.md#a-nodes-own)). ## A node refused a version @@ -76,6 +77,7 @@ record. * **An event waits** (`waiting` when put): the node lacks an event it builds on. It takes it once that one arrives. * **It doesn't start**: its store file doesn't read, or an option of a swarm that isn't - federated is set ([`running-a-node.md`](running-a-node.md), Its options). -* **A write is refused**: [`writing-and-reading.md`](writing-and-reading.md), Why a write - is refused. + federated is set ([`running-a-node.md`](running-a-node.md), + [Its options](running-a-node.md#its-options)). +* **A write is refused**: [`writing-and-reading.md`](writing-and-reading.md), + [Why a write is refused](writing-and-reading.md#why-a-write-is-refused). diff --git a/docs/guides/federation/writing-and-reading.md b/docs/guides/federation/writing-and-reading.md index 0a04773..3dd0578 100644 --- a/docs/guides/federation/writing-and-reading.md +++ b/docs/guides/federation/writing-and-reading.md @@ -1,8 +1,9 @@ # Writing and reading A party writes values at places, through its client; anyone a node lets in reads what -counts there. The rules are the design's ([`federation.md`](../../federation.md), The -policy, What counts). +counts there. The rules are the design's ([`federation.md`](../../federation.md), +[The policy](../../federation.md#the-policy), +[What counts](../../federation.md#what-counts)). ## Places @@ -36,7 +37,7 @@ or `waiting` for an event it builds on that the node doesn't hold yet. A write counts while the key that signed it is among its party's keys: those of its key set, or, while it has written none, those its version names -([`federation.md`](../../federation.md), Keys). +([`federation.md`](../../federation.md), [Keys](../../federation.md#keys)). ## What counts -- cgit v1.3.1