7 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	af66adc180	Bring in the adoption handing (fix/1945-adopt-hashes 17478994): the have's user list carries Handed beside Follows and Key; a state that names readers is not Readable to a composer that knows no readers (review of the switch, issue 1945)	2026-10-26 12:23:07 +01:00
jschoubben	175a5567b8	The bus node follows the grants part's sealed user list, and only the grants part reads the vault's hashes (ADR 0547 clauses 7, 9; issue 1945) ... The grants part writes its list as an object of its own bucket, sealed to the bus node's key, and names it in user-list.sealed; the node-engine of the node holding mesh-broker is granted that one key and an object by name, the grants part its bucket (the controller's copy carries the same grants, byte for byte, golden regenerated there). A state may name its readers (announce, NamedReaders): mesh-vault.bus-accounts is read by mesh-grants alone.	2026-10-26 11:53:11 +01:00
jschoubben	1747899419	delivery: the bus node hands the loaded list's hashes to the vault, sealed, in the bus module's have (ADR 0547 clause 9, issue 1945) ... The vault holds no value for the controller's own account, the node accounts and the enrolled devices, so it cannot hash them; the one part that has their hashes is the node-engine of the bus node, in the list the bus loaded. The have of the bus module now carries that list's hashes sealed to the vault's key (UserListWritten.Handed), which every reader of the have bucket sees as a count, a list digest and a key fingerprint, and only the vault opens. HandedAccountsOf reads them from a composed list, HandAccounts seals, OpenHanded opens and refuses a box sealed to another key.	2026-10-26 11:28:38 +01:00
jschoubben	0be0ffd615	Compare the have's user list by what it says, so a have is not written again for the same list (ADR 0547 §8)	2026-10-25 21:47:30 +01:00
jschoubben	f63fa86c74	Say in the bus module's have the user list its node wrote alone, so the bridge of ADR 0547 §8 reports what the bus loads (issue 1945)	2026-10-25 21:42:13 +01:00
mesh-tools	ba684e5497	Give each asking of a merge ask its own id, and add the have phase removed (issues 1370, 1369) ... The router drops an ask under an id it keeps as a redelivery, so a gate that writes the same group's ask again at unchanged heads was never heard. Ask gains Asking; AskingID gives the first asking the old id and later ones their own. PhaseRemoved lets the node-engine say a module left its node.	2026-10-20 01:18:49 +00:00
jschoubben	2b420603fe	Give delivery's keys and values one home the node-engine and the parts read (issue 1131)	2026-10-18 18:49:24 +02:00