From a1a9d8c537864298046bd4273725e7dde0de1dcf Mon Sep 17 00:00:00 2001 From: tv Date: Mon, 16 Nov 2026 04:12:41 +0000 Subject: federation: `{party}` matches only a party's name Where a rule's `{party}` segment met a segment naming no party, one builder would match it with a writer that is nobody, another wouldn't match and let a later rule decide, and the two would judge a write at `names/r/foo` apart where a `names/r/*` rule follows. It doesn't match, which is the reading the wiki example needs. --- docs/federation.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'docs/federation.md') diff --git a/docs/federation.md b/docs/federation.md index 56113ad..2e237be 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -158,8 +158,9 @@ Spread out: version and a fork's set those of the parties that start it (Nodes). * **The rules**, in order: the first whose path matches a path says who writes there. A path is segments separated by `/`, none empty. A rule's first segment is literal, - and not `_continuum`; any other is literal, `{party}` (a party's name, once in a rule - at most), `*` (any one segment) or, last only, `**` (one segment or more); none is + and not `_continuum`; any other is literal, `{party}` (the name of a party of the + version, once in a rule at most: a segment naming none doesn't match, and a later rule + decides), `*` (any one segment) or, last only, `**` (one segment or more); none is `@`. A rule matches a path key by key: a key holding `/` is one segment, which only `*` and `**` match. The writer is `"{party}"` (the party the path names, only where the rule's path holds `{party}`), a party of the version, or `false`: nobody. A path @@ -651,6 +652,7 @@ What an attacker does, and what happens. *Unit*: the judging, with crafted chang | 67 | A key its party dropped writes, from a history before the drop, ahead of what the party signed | Counts no more, and takes out nothing the party signed again after the drop | unit | | 68 | A coordinator shows one of two decisions for an epoch to some nodes, the other to the rest | Each follows the one it holds; a node holding both follows neither; their operators bring them together | sim | | 69 | A party's `true` and `false` on one proposal, both in a history | Both count there: a history holding more votes takes back no pass and no death | unit | +| 70 | A path whose `{party}` segment names no party (`names/r/foo`) | The `{party}` rule doesn't match; a later rule decides | unit | ## Roads not taken -- cgit v1.3.1