L3: mesh-vault mints, retires and signs; nats makes its certificate; messenger asks each engine (issue 774, ADR 0561), rebased onto L2 #556

Merged

mesh-tools merged 19 commits from feat/774-vault-mints-l2 into main 2026-10-29 07:44:23 +00:00

Conversation 7 Commits 19 Files Changed 48

+3463 -153

19 Commits

Author	SHA1	Message	Date
jschoubben	add6f143ca	mesh-delivery-gate: an answer stands only for the ask it answers, and a merge never handed says why ... On 2026-10-29 the group feat/774-vault-mints-l2 was approved and never handed: hq#495 kept a Decline of an earlier ask beside the Approve of the next, readyAsks skipped it and handTurn returned nil for every member, with no log line. The Approve and a new ask now clear an earlier Decline, a run's answer names its ask (answered_ask), an approved merge that waits for nothing and is not handed logs why once and is a stalled line, and delivery_turns lists no unwritten turn while the check gates no merge.	2026-10-29 02:15:34 +01:00
jschoubben	b46089b698	Merge remote-tracking branch 'origin/main' into l3-mc-main	2026-10-29 02:15:33 +01:00
jschoubben	c193d2b389	Pin mesh-sdk 8eafc0c, the L3 group's head on mesh-sdk main with #120 and #121 (issue 774)	2026-10-28 21:56:06 +01:00
jschoubben	10447d8c1e	mesh-config reads the placement beside the controller's assignments while both stand, as L2 has it and the vault does, and is listed as a reader of them (issue 774, ADR 0549 §5; re-review)	2026-10-28 21:54:36 +01:00
jschoubben	5be6576117	Follow L2 under L3: the vault and mesh-config read the seat mesh-placement's placement, and the check that only listed modules read the controller's assignments moves into noplacement, as L2 deleted the placement check (issue 774, ADR 0567, ADR 0549 §3, §6)	2026-10-28 21:54:36 +01:00
jschoubben	24fad2b92a	mesh-vault: pin mesh-sdk 4e6e5cc, the L3 group's head rebased on L2 (issue 774)	2026-10-28 21:54:36 +01:00
jschoubben	d3eb5cae80	mesh-vault: secret-ask answers the callers its manifest names, each named as the runtime proved it, within the same bounds; the controller's relay as before (issue 774, ADR 0563 §8)	2026-10-28 21:54:36 +01:00
jschoubben	2043200201	messenger: ask each machine's own engine whether it is root-free, the node seat node-engine's root-free, not the controller's (issue 774, ADR 0563 §6)	2026-10-28 21:54:36 +01:00
jschoubben	ef618e8199	nats: the bus's certificate command moves here from mesh-controller with the same output, made once and checked, so the bus module makes its own certificate when a mesh is raised from nothing (issue 774, design 47 L3 s11)	2026-10-28 21:54:36 +01:00
jschoubben	c00005c141	mesh-vault signs: its signing key and authority made once with their operator copies, the verb sign for a node's own certificate from bus state, the event signed, the state signers and the tools that read and reassert them (issue 774, ADR 0550 §2)	2026-10-28 21:54:36 +01:00
jschoubben	bd5f170af0	The placement check's list of modules still reading the controller's assignments only shrinks against the trunk's copy (issue 774, ADR 0529 clause 2)	2026-10-28 21:54:36 +01:00
jschoubben	6bbb8329e4	mesh-config resolves for the modules the catalogue's placement puts on a node alone, and the placement check refuses any other module that reads the controller's assignments unless listed with why (issue 774, ADR 0549 §3, §6)	2026-10-28 21:54:36 +01:00
jschoubben	e6b913cac7	mesh-vault: account_retire refuses while the controller holds the lease or before the wants are read whole, as the passes do (issue 774, review round 1)	2026-10-28 21:54:36 +01:00
jschoubben	411c1b8de8	mesh-vault: prove the vault whole on a real bus mints only from the lease write, and try a failed mint again at the pass; adopt the operator key before the watches open (issue 774, ADR 0561 §1-§4)	2026-10-28 21:54:36 +01:00
jschoubben	64e6688ec8	mesh-vault: tell where modules stand and which node holds the bus from the catalogue's placement first, so the vault does not depend on the controller's assignments for them (issue 774, ADR 0549 §3, §5)	2026-10-28 21:54:36 +01:00
jschoubben	2d57c9663a	mesh-vault: serve issue-account, the hand path that mints one wanted account now, and record a rotation at most once per loaded list's revision; a covered account still never rotates in place (issue 774, ADR 0561 §4, §9)	2026-10-28 21:54:36 +01:00
jschoubben	5c1729523b	mesh-vault: retire an account the grants part no longer wants only within ADR 0230's bounds, keeping its value, and re-enable it when wanted again; account_retire for a person past the bound (issue 774, ADR 0561 §2)	2026-10-28 21:54:36 +01:00
jschoubben	1628db6c80	mesh-vault: mint only while the controller's lease is handed away, read afresh before each mint, and say in vault_status what is held back and why (issue 774, ADR 0561 §3, §9)	2026-10-28 21:54:36 +01:00
jschoubben	0b9f19b612	mesh-vault: mint each account the grants part wants and the vault holds no value or adopted hash for, in the controller's shape, hashed before account-issued and secret-changed (issue 774, ADR 0561 §1, §2, §4)	2026-10-28 21:54:36 +01:00