13 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	c28c645ca4	Name the node-engine's data items state, so mesh-host writes and disk-load reads one shape (ADR 0577) ... The contract (state name, key form, value) is in delivery; buscompose grants the engine its own node's keys of mesh-host_data and each node's disk-load a read of its own node's keys alone, the same way the engine's other states are granted. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-01 00:05:38 +01:00
jschoubben	ef1ec1c935	Name mesh-config among the controller's lease readers (issue 774) ... mesh-config reads mesh-controller.lease to take the config over only once the lease is handed away (ADR 0561 §3, its takeover.go leaseAway), and was refused it as a reader the composer does not name.	2026-10-30 18:26:23 +01:00
jschoubben	e703e9b0e2	Judge every read for its reader where the bus's users are composed (issue 774) ... Since 13:25 the vault, the assigner, the watchman, the grants part and the artifact store's tools were refused mesh-controller.lease, and the vault mesh-grants.accounts, though the composer names them those states' readers (ADR 0547 clause 9): the controller splits reads with its own copy of the reader-less ReadsAnnounced, which knows no named readers, and Users only moved reads from granted to refused, never back. Quick fix: the controller calls ReadsAnnouncedBy with the module. Thorough fix, chosen because the kind was met on four owners and the judgement had two copies: Users judges every read again for its reader against the announcements in Records (withAnnouncedReads), whatever split the caller made, and the reader-less ReadsAnnounced is removed so no caller can judge without the reader. A rule over manifests was not added: ADR 0495 clauses 1 and 5 keep readability out of the manifest and replaced the merge gate's reads check by each module's announcement test. gitea.bound and disk-load.readings stay refused: their owners announce them not readable, which their own code fixes.	2026-10-30 18:08:02 +01:00
jschoubben	007b6fd45f	Drop stdio.Discover, the self-check's discovery and its read of the withheld hearings, which no probe uses now that the operator dropped D-root, D3 and D-heard (issue 1952)	2026-10-30 00:02:07 +01:00
jschoubben	7bd0f6c2bd	Name the artifact sweep's seat mesh-artifact-sweep for its scope, grant the provisioner client its machine's plans in place of the needs, and keep the grants part's withheld hearings in one layout, so the seat names follow ADR 0121 and the client and the self-check read the bus (issue 1955, ADR 0571 clause 2, ADR 0570 clause 2)	2026-10-29 23:53:51 +01:00
jschoubben	dc78524e38	Let the artifact store's seat holder read the controller's lease, so its sweep starts only once the lease names no controller (issue 1955, ADR 0571 clause 2)	2026-10-29 23:10:46 +01:00
jschoubben	7df90445ad	Add the seats mesh-wants and mesh-hand-acts, the engine's packages verb, the act layout and a recorder that falls back to the controller's log while the seat has no holder, so the control records have homes the lease does not hold (issue 1953 L5-S1, S2, S4)	2026-10-29 22:09:16 +01:00
jschoubben	5a47192b57	Grant the health holders what ADR 0564 gives them and nothing more: named reads of the lease and the controller's conditions and hand acts, the watchman's own dead-letter consumer, and the bus tools' removal account (issue 1952 S5)	2026-10-29 21:40:49 +01:00
jschoubben	1386219d4d	One reader of the catalogue's placement and the toolchain gate over it, in place of the three copies over the controller's assignments (issue 774, ADR 0549 §3, issue 1940); the assigner may read the lease (ADR 0549 §5)	2026-10-28 21:54:04 +01:00
jschoubben	0062bdc4a6	buscompose: the assigner may read the controller's lease, to choose where grants are read from (issue 774)	2026-10-28 21:54:04 +01:00
jschoubben	fefa8b88ea	Say when the lease is handed away, let the vault and the grants part read it, and let the grants part create the consumers an account needs, so both turn on at the lease write alone (issue 774, ADR 0561 §3, §6)	2026-10-28 21:54:04 +01:00
jschoubben	da506bb3b8	Say which bus accounts the grants part wants, in a state only the vault reads, and what the vault says when it mints one, so the vault can mint from the grants part's word (issue 774, ADR 0561 §2)	2026-10-28 21:54:04 +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