novox/hq
18
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Design 47: the node-record read is the composer copy's one intended grant beyond the controller's, and what a hand-back means for it (issue 1126, ADR 0555)
mesh/delivery closed: a newer head of the same pull request
Details
mesh/check checking 5bb109e36ea7 on 515c405c8939 | novox/hq#482 in group feat/1126-nodes-compose

Browse Source
This commit is contained in:
jschoubben
2026-10-26 18:33:46 +01:00
parent d948774794
commit 5bb109e36e
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md
+6 -1
View File
@@ -703,7 +703,12 @@ backup holder backs up nothing, and the have says so.
public halves of its sealing and serving keys, the certificate issued for its internal name, its outward links public halves of its sealing and serving keys, the certificate issued for its internal name, its outward links
and networks, and its node-engine's contract. Written at start and when an observed fact changes, only when it and networks, and its node-engine's contract. Written at start and when an observed fact changes, only when it
differs (ADR 0555 §3). Whether the hub took its found tunnel over, and which node enrolled under a carried differs (ADR 0555 §3). Whether the hub took its found tunnel over, and which node enrolled under a carried
peer's key, are read from the placement and the records together, never written. peer's key, are read from the placement and the records together, never written. Every node's account reads
every node's `<node>.node`: a grant the grants part's composer gives and the controller's frozen copy does not.
Since the take-over the grants part's list is the one the bus loads; after a `hand-back` the controller's list
holds, without that read, and nodes keep applying while composing their own fails loudly until the next
`take-over`. mesh-sdk's composer test holds the copy to every grant of the controller's golden plus exactly that
read and the bucket-creation advisories of issue 1790.
- **Composed again on events, never on a timer.** A changed input at the same fingerprint (a setting or given - **Composed again on events, never on a timer.** A changed input at the same fingerprint (a setting or given
value, a secret rotated or moved, a credential issued, a provider's contribution, a peer added to the hub) is value, a secret rotated or moved, a credential issued, a provider's contribution, a peer added to the hub) is
composed again when its event is heard, and applied as a revision of what runs (ADR 0547 §2). composed again when its event is heard, and applied as a revision of what runs (ADR 0547 §2).