From 12418f51961bd74f9924a1046e04c503172c08ae Mon Sep 17 00:00:00 2001 From: tv Date: Mon, 16 Nov 2026 04:12:55 +0000 Subject: federation: a map made only on the way to what a change writes A change wrote nothing where rules say who writes but `@` keys and the maps on the way to them, never deleting or replacing one. It didn't say that a map is made only on the way to an `@` key the same change writes: one builder would take any member's maps in any party's namespace, left empty for good, another wouldn't. Nor that a map is made only where none is: a map made where one is, naming it as replaced, hides what it held, votes under `_continuum/federation` among them. Both are said, for the federation's own paths too. --- docs/federation.md | 25 ++++++++++++++----------- 1 file changed, 14 insertions(+), 11 deletions(-) (limited to 'docs') diff --git a/docs/federation.md b/docs/federation.md index 2e237be..281a064 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -168,16 +168,17 @@ Spread out: A **place** is a path a rule matches. Its value is the envelope in its `@` key (`names/r/tv/toaster/@`). An envelope goes only in an `@` key, an `@` key never holds a -map, and a change writes nothing else where rules say who writes but the maps on the -way to `@` keys, never deleting or replacing one: so no key is both a value and the way -to places, whatever the rules of any version say, and a version may give a place and -places below it alike. Nothing is written within a list. How names and addresses are -spelled as paths is the application's: the registry writes a name by its labels, last -first (`names/r/tv/toaster` for `toaster.tv.r`, `names/r/tv` for `tv.r`), and an -address by its parts, so that a party's zone or block takes a rule or two. Rules go by -first match, so a party named like a shared name takes it where a `{party}` rule comes -before it: the application keeps party names apart from its spelling (no party named -`wiki` while `wiki.r` is lass's). +map, and a change writes nothing else where rules say who writes but the maps on the way +to the `@` keys it writes, each only where none is, never deleting or replacing one: so +no key is both a value and the way to places, whatever the rules of any version say, a +version may give a place and places below it alike, no map is left empty, and no change +plants keys in another's namespace. Nothing is written within a list. How names and +addresses are spelled as paths is the application's: the registry writes a name by its +labels, last first (`names/r/tv/toaster` for `toaster.tv.r`, `names/r/tv` for `tv.r`), +and an address by its parts, so that a party's zone or block takes a rule or two. Rules +go by first match, so a party named like a shared name takes it where a `{party}` rule +comes before it: the application keeps party names apart from its spelling (no party +named `wiki` while `wiki.r` is lass's). A version is none if its bytes aren't the JCS encoding (RFC 8785) of the JSON they read as, so that nothing in it is spelled two ways and no key is there twice; if a field is @@ -189,7 +190,8 @@ is written as one, so that nodes knowing more of what a version may say don't pa those knowing less. The federation's own paths are its number's, not the rules': the same in every -version. They hold their values directly, and never nest. +version. They hold their values directly, and never nest; a change makes the maps on +the way to what it writes there as it does to `@` keys. | Where | What | Who writes it | |---|---|---| @@ -653,6 +655,7 @@ What an attacker does, and what happens. *Unit*: the judging, with crafted chang | 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 | +| 71 | A map made where no `@` key is written below it, or where one is (hiding what it holds) | Refused | unit | ## Roads not taken -- cgit v1.3.1