2706 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
jschoubben	077135a7f3	Keep mesh-config's held values in mesh-sdk's KeptValue layout, which the checks read, and pin mesh-sdk 66ff33d (issue 1953) ... The layout and its keys are unchanged, so no value moves.	2026-10-29 22:41:29 +01:00
jschoubben	4117ec3a57	Serve compare, take-over and hand-back as the mesh-config seat's verbs, beside the module's own tools; pin mesh-sdk 4204afd (issue 1953)	2026-10-29 22:29:48 +01:00
jschoubben	45db0e650e	Record a drill in mesh-hand-acts and count S15 over both logs, so the healers no longer refuse a drill (issue 1953)	2026-10-29 22:27:23 +01:00
jschoubben	d34645361d	Build config's switch from the controller's records: declared, compare, take-over and hand-back, so the operator approves the last move only once nothing differs (issue 1953) ... compare also resolves every placed module's values on every node both ways, as ADR 0565's insight of 2026-10-29 asks after #558. After the take-over the predefined list and pull requests' config come from the indexer and pull-declares is refused; a hand-back returns to the mirrors until the lease write. From the lease write a trusted value is set only on an Approve. Acts are recorded through mesh-hand-acts. Pins mesh-sdk 2e5cc4f.	2026-10-29 22:27:23 +01:00
jschoubben	0842361f85	Keep the hand-act log's acts 400 days, as ADR 0565 §10 has it, now that a module log may say its age; pin mesh-sdk 2e5cc4f (issue 1953)	2026-10-29 22:18:59 +01:00
jschoubben	371abdaad1	Wait on keys that expire on the bus instead of in-process timers, so the healers' settles and S15's fortnight survive a restart (issue 1952) ... A settle and the fortnight end are keys of wakes whose time to live is the wait, heard on expiry; attempts and would keep each key a week by its own time to live. Rearm stays only for a settle that expired while no instance watched. Pins mesh-sdk bc6c8a6.	2026-10-29 22:17:29 +01:00
jschoubben	4cbdd0fc74	Give each delivery's hold bound its own key's time to live and map a seat's finding to the module the placement says holds it, so the keeper holds the right findings for the right time (issue 1952 C7)	2026-10-29 22:16:23 +01:00
jschoubben	b5fdcb88c8	Say checked, healer-acted and act-recorded on their seats' subjects, where their consumers hear them, and pin mesh-sdk fbd00c8 (issues 1952, 1953) ... stdio.Emit put them on the module's subject, which no consumer of a seat's event hears. The manifests no longer list a seat's events as the module's own, which the SDK now refuses. mesh-hand-acts takes its act layout and names from mesh-sdk's handacts, and counts a repeated cause by its Repair rule.	2026-10-29 22:12:08 +01:00
jschoubben	d632461eb9	Add the condition keeper, mesh-conditions, so conditions are raised and cleared from the observers' findings without the controller's lease, held while their module is delivered, and switched only on the operator's take-over (issue 1952 C1-C8, ADR 0564)	2026-10-29 22:05:45 +01:00
jschoubben	5b2b70cd6c	Keep the hand-act log as mesh-hand-acts' module log, the stream ADR 0565 §10 names, so every act is held in its order (issue 1953) ... The warrants stay a bucket and no longer age, so a warrant is recorded once; one whose act was lost is written again from the router's record. hand-acts says the log's fill against its cap.	2026-10-29 21:56:42 +01:00
jschoubben	e1cdeebcdf	Add mesh-hand-acts, holder of the seat mesh-hand-acts, so the hand-act log has a home the controller's lease does not hold (issue 1953) ... Acts are kept 400 days under the runtime-proven caller and said as act-recorded; a warrant is read from the router's own record and recorded once per ask; hand-acts answers over both logs. The act layout is a copy of mesh-sdk's until L5-S2 lands.	2026-10-29 21:54:21 +01:00
jschoubben	9dd27d2edb	Re-arm every running settle from the attempts kept when the healers start, so a restart loses no wake (issue 1952) ... A settle that ended while they were down is judged at once. The README says the week-long bucket age is the deleter of would and attempts for this release.	2026-10-29 21:49:46 +01:00
jschoubben	885b7a3a8e	Pin checks/health to the group's mesh-sdk 69fcb6c, so it knows the health seats the new modules claim (issue 1952)	2026-10-29 21:49:46 +01:00
jschoubben	4c11c2c0c0	Move the healers out of the controller into mesh-healers, acting on the keeper's events and only once the lease names no controller (issue 1952) ... Until the lease write each act is written to would, kept a week by its bucket's age, so a would-act counts for no budget or brake. Acts begin by a create in attempts; H3 asks the grants part's assert; the brake and S15 are its own findings.	2026-10-29 21:48:09 +01:00
jschoubben	babe2f194a	Write the self-check's findings and checked in mesh-sdk's health layout, so the condition keeper reads them as it reads every observer's (issue 1952) ... Pins the group's mesh-sdk head 69fcb6c. A seat verb's run="true" is taken as the seat schema gives it.	2026-10-29 21:48:09 +01:00
jschoubben	d7247eae19	Move the self-check out of the controller into mesh-self-check, so its runs and findings no longer need the controller's lease (issue 1952) ... The probes whose facts are on the bus run with their assertions unchanged (D6, D7, D15, DW, H-bus); the rest answer deferred, naming what they lack, never a pass. Findings go to its own bucket for the condition keeper; each run is kept a week and said as checked. The finding layout is a copy of mesh-sdk's S3 until that lands.	2026-10-29 21:43:55 +01:00
jschoubben	16378e0850	Take mesh-config off the assignments readers: since #558 (issue 1953) it reads placement and its modules' manifests alone (issue 774)	2026-10-29 21:08:02 +01:00
jschoubben	071429c3be	Pin mesh-sdk 22c9ddd in mesh-vault, the L3 re-land group's sdk head (issue 774)	2026-10-29 21:08:02 +01:00
jschoubben	3dd7b734aa	Revert "Merge pull request 'Revert L3: its node-engine removed every held module on novox, the bus server among them (issue 774)' (#557) from revert/774-l3 into main" ... This reverts commit 030f9ee4e7, reversing changes made to 1555241393.	2026-10-29 21:05:14 +01:00
mesh-tools	96b129e544	Merge pull request 'mesh-config: read config declarations from each placed module's own manifests on the bus, never from the controller (issue 1953)' (#558) from fix/1953-config-from-builds into main	2026-10-29 19:47:55 +00:00
jschoubben	0d71d8b56c	Move the head so the checker takes #558 again: a reopened pull request is not taken back as a candidate (recovery of de-spiegel, operator's yes 2026-10-29 17:56 CET)	2026-10-29 18:10:27 +01:00
jschoubben	96a37f58ca	mesh-config: read declarations from each placed module's own manifests as built, and placement alone, so a module from its own repository resolves (issue 1953) ... The controller's declared-config mirror never held de-spiegel's keys, and Resolve skipped an assigned module it held no declarations of, silently: de-spiegel stayed held on novox with its values set. Declarations now come from the indexer's trunk manifest with the wanted build's laid over it per node; which module runs where from the seat mesh-placement alone. A placed module with no readable manifest is listed as unresolved with why, logged, and keeps its last resolved values.	2026-10-29 15:19:24 +01:00
mesh-tools	030f9ee4e7	Merge pull request 'Revert L3: its node-engine removed every held module on novox, the bus server among them (issue 774)' (#557) from revert/774-l3 into main	2026-10-29 08:59:53 +00:00
jschoubben	c8240c38bb	Revert L3 (mesh-catalog, merge 15552413): its node-engine removed every held module on novox, the bus server among them, at 08:54 CET on 2026-10-29 (issue 774) ... L3 lands again with two fixes: a held module is never removed, and the grants cover L3's new subjects.	2026-10-29 09:42:30 +01:00
mesh-tools	1555241393	Merge pull request 'L3: mesh-vault mints, retires and signs; nats makes its certificate; messenger asks each engine (issue 774, ADR 0561), rebased onto L2' (#556) from feat/774-vault-mints-l2 into main	2026-10-29 07:44:23 +00:00
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
mesh-tools	158348ede7	Merge pull request 'mesh-delivery-gate asks the operator's Approve on a verdict only: the one-hour fallback goes (issue 1733)' (#555) from fix/1733-no-hour into main	2026-10-28 21:29:52 +00:00
mesh-tools	ff4c6c0435	Merge pull request 'The Go, Node and image build modules watch their settings file and say a capacity of 0 in their health' (#554) from fix/park-wakes into main	2026-10-28 21:03:17 +00: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
mesh-tools	39ce149f74	Merge pull request 'mesh-build-go's compose integration test gives its module one slot (issue 1126)' (#553) from fix/1126-capacity-transition into main	2026-10-28 20:24:49 +00:00
jschoubben	f37f93e812	Drop the unreachable 'before its check ends' caveat (issue 1733)	2026-10-28 21:00:09 +01:00
jschoubben	cf4879eaa1	Ask the Approve when the check's verdict arrives, not after an hour (issue 1733)	2026-10-28 20:59:46 +01:00
jschoubben	1e377fe862	Go build module: the compose test gives its module a slot, since a node with no capacity set now pulls nothing (issue 1126, ADR 0567 §15) ... The test built its module with no settings file and no Capacity; the new buildstep.NodeCapacity answers 0 for that (no default names a node), so the puller took no ask and the test timed out after 90 s in check 205f634c30df. Failed first locally at origin/main af89893d (90.1 s), passes with the slot (2.5 s).	2026-10-28 20:23:42 +01:00