summaryrefslogtreecommitdiffstats
path: root/docs/openapi.yaml
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 14:13:39 +0000
committertv <tv@krebsco.de>2026-11-19 15:18:52 +0100
commit841897b79838f97a809356471baf2f41e186cdfa (patch)
tree6fb5e0ac21b69986c87e8d87e87806ff514b451f /docs/openapi.yaml
parent27b76d5748f23a879d9fc82c725a58b514020ef9 (diff)
continuum-party: which places a proposal gives another writer
Rules go by first match, and `{party}` matches only the names of the version's parties: admitting a party named as a segment of a place, or changing the rules or their order, moves who writes the places below it, and what their writer wrote there counts no more once the version passes. Nothing said so: a proposal showed only its fields' changes. `client::writers` names, of the places holding a value, those whose writer a version changes, as `place: before -> after` (`nobody` where no rule gives it one). `continuum-party proposals` prints them under each proposal's changes (`who writes …`), and a fork's check does for the fork's version (`writers` in POST /events/fork). The guides and federation.md say so; row 72 is tested (`federation_attack_72`).
Diffstat (limited to 'docs/openapi.yaml')
-rw-r--r--docs/openapi.yaml10
1 files changed, 8 insertions, 2 deletions
diff --git a/docs/openapi.yaml b/docs/openapi.yaml
index 6cef2f2..b5e7b14 100644
--- a/docs/openapi.yaml
+++ b/docs/openapi.yaml
@@ -1696,7 +1696,9 @@ paths:
events it took that are neither among them, nor in their history, nor above
them); what the fork's version changes of the version current at those heads, a
line each as `field: before -> after`, its rules among them, `keys` and `nodes`
- party by party (`changes`); and the parties whose keys the fork's version gives
+ party by party (`changes`); of the places holding a value there, those whose
+ writer the fork's version changes, as `place: before -> after`, `nobody` where no
+ rule gives it one (`writers`); and the parties whose keys the fork's version gives
otherwise than they
had at those heads, each with its keys there and in the fork. A node that
doesn't hold that history takes a fork's root on its operator's word, who names
@@ -1715,7 +1717,7 @@ paths:
application/json:
schema:
type: object
- required: [fork, builds, why, lacking, changes, keys]
+ required: [fork, builds, why, lacking, changes, writers, keys]
properties:
fork:
type: string
@@ -1732,6 +1734,10 @@ paths:
type: array
items:
type: string
+ writers:
+ type: array
+ items:
+ type: string
keys:
type: object
additionalProperties: