10 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	85ba0a9a70	A node record states the reader capabilities its engine reads, a module value the ones its manifest needs, and a want of rule 9 or 10 reads (ADR 0614 §2, §4, issue 774) ... NodeRecord.ManifestReads (`manifest-reads`) and Module.Needs (`needs`) are additive at Version 1, read leniently by every running part. checkRule takes 1 to 10 so a later release may number the verb wait and the capability hold; nothing writes 9 or 10 in this one. kept_until_delivered.go stays: this release still builds beside mesh-host 798d73e, and its head comment names the next mesh-sdk release as the one that removes it. Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn	2026-11-03 23:18:22 +01:00
jschoubben	43d499b0b3	Remove what nothing calls once the controller's repository is emptied: facts, the src1 computation, the recreation judge, and the build step's dead helpers (ADR 0593 §11) ... Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 18:58:28 +01:00
jschoubben	dcb2e6e966	Remove the controller from the delivery contract, and its command line client and hand composer ... The controller ended (ADR 0590): the grants issued are the grants part's alone, so its grant value is Grant and GrantSource goes; a node trusts the vault's key alone, follows the grants part's user list alone and composes its own or none; the controller's composed and builds bucket names go. nox calls seat verbs (ADR 0590 clause 7), so the cli package that spoke to the node-engine's socket goes, and mesh-hand-compose, which wrote the controller's compositions. A have an engine from before wrote, composes controller, still reads. Issue 1126 B4a, B6. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 11:36:26 +01:00
jschoubben	6e39ed1852	Refuse a want's rule past the eighth in the refusals table, now that the eighth rule exists (issue 1954 D1)	2026-10-29 22:37:41 +01:00
jschoubben	a1a688b19e	delivery: the grants part's grant keys and the source the assigner reads (a1; issue 774) ... Why: the grants part writes grants.<module>.<fp> in shadow beside the controller's; the assigner switches source only when the lease is handed away.	2026-10-28 21:54:04 +01:00
jschoubben	20a6dc4920	A grant says whether it names a module's accounts on a node, for the assigner and the compose verb (ADR 0546)	2026-10-25 20:50:51 +01:00
jschoubben	c4f37c279a	The assigner's seat with put, release and puts, the controller's compose verb, a put's key and value, and the view answers no option that authorises (ADR 0546)	2026-10-25 20:49:29 +01:00
jschoubben	d6cef5829b	Have a want name its composition and a backup answer; give the node its own want, the seventh rule, the held phase and the backup and record asks (issue 1943, S3) ... The node agent applies only the composition its want names, and the assigner writes a want only once that composition exists (ADR 0539 clauses 1, 6, 14 and 16).	2026-10-24 16:29:24 +02:00
jschoubben	687d715e99	Lay out the controller's grants and the assigner's composition verdict under the checker's key, so the assigner's rule 6 and the checker's composition read one layout (issue 1297 subtask B1b, issue 1394; ADR 0528 clauses 2 and 5)	2026-10-23 15:11:34 +02:00
jschoubben	ec2bd3b990	Lay out the assigner's wants, holds and differences in mesh-sdk, so the assigner, the watchman and the view read one layout (issue 1297, subtask B1a; ADR 0528 clauses 1 and 4)	2026-10-23 15:10:09 +02:00