R6: the node-engine applies from its wants and signed compositions, one module at a time; operator-signers (issue 1944) #134

Merged

jschoubben merged 21 commits from feat/r6 into main 2026-10-24 23:17:39 +00:00

Conversation 1 Commits 21 Files Changed 69

+3808 -4749

21 Commits

Author	SHA1	Message	Date
jschoubben	81758b24a8	Pin mesh-sdk to feat/r6 748c564, which carries main's composer (issue 1943)	2026-10-24 23:06:00 +02:00
jschoubben	25ad5ce42c	Merge remote-tracking branch 'origin/main' into feat/r6	2026-10-24 23:00:09 +02:00
jschoubben	b47df31834	Pin mesh-sdk to d7a9b96	2026-10-24 21:18:33 +02:00
jschoubben	fd05c8235d	Pin mesh-sdk to 7f9cc0e	2026-10-24 20:43:47 +02:00
jschoubben	98d1f165b7	Pin mesh-sdk to e45bdc0	2026-10-24 20:22:00 +02:00
jschoubben	332d8f161b	The carried genesis template no longer lists the controller's plan-moved event	2026-10-24 18:32:58 +02:00
jschoubben	5088755e5e	gofmt	2026-10-24 18:28:22 +02:00
jschoubben	e72c682450	Pin mesh-sdk to a523a8c	2026-10-24 18:18:06 +02:00
jschoubben	be5f31ce66	What runs is the agent's compositions plus the kept declaration's rest: health, filling, take act, directories and the others held out of an apply read it; a restart trusts the node-engine's own haves; the bed tests run off Arch (review round 1)	2026-10-24 18:13:40 +02:00
jschoubben	67db003813	Pin mesh-sdk to the head of feat/r6 (5da87a0)	2026-10-24 17:50:20 +02:00
jschoubben	e5a06cc73d	The node agent waits for a backup's end on the holder's event, not by polling; the manifest consumes it (R6-A A5)	2026-10-24 17:03:30 +02:00
jschoubben	20d0998cdd	The operator's public keys reach the node as the file operator-keys, fed by the node-engine's setting operator-signers (ADR 0539 clause 3)	2026-10-24 16:57:15 +02:00
jschoubben	83f16cff8d	apply FILE is no hand path: mesh-compose and a want are (ADR 0539 clause 10); genesis keeps the carried bundle	2026-10-24 16:55:23 +02:00
jschoubben	96d0322498	The node-engine reports reads-wants; a failed apply is said; the have's fingerprint and digest follow its health (R6-A A6)	2026-10-24 16:43:26 +02:00
jschoubben	b2003e7a38	A composition is applied only when the controller or the operator signed it; the node agent's integration tests on an embedded bus (R6-A A9, A1, A5)	2026-10-24 16:42:11 +02:00
jschoubben	3303797bfb	The node agent runs in the node-engine: watches the wants and compositions on the link, applies one module's composition, asks the backup, writes the haves (R6-A A1, A5, A6)	2026-10-24 16:39:51 +02:00
jschoubben	d5dd7761c6	The node agent: follows the wants and the node's compositions, applies one module at a time, backs a data module up first, holds it on a failed backup (R6-A A1, A2, A5, A6)	2026-10-24 16:36:21 +02:00
jschoubben	5f5f37b0b2	Pin mesh-sdk to feat/r6 S1-S3 (d6cef58): the composition bucket, the want's composition and backup answer, the have's composition and held phase	2026-10-24 16:31:20 +02:00
jschoubben	c30b86ae22	Proved: the evidence is a have under the running build (comment)	2026-10-24 16:26:39 +02:00
jschoubben	1598156752	The node-engine hears no declaration: the queue, orders, put-backs, unsaid, numbers and news go; a session says the facts in the node-engine's own order, and the first have proves a build (R6-A A7, A8)	2026-10-24 16:25:11 +02:00
jschoubben	e2b6f37168	Apply one module at a time: a scope of the module and what the others hold, and an owner record, so a removal is the module's own (R6-A A3, A4)	2026-10-24 16:16:32 +02:00