397 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	ba398e2460	Answer a placement candidate as ADR 0559 has it: added and removed modules, per-module refusals, both digests of a difference, and a node's read of every candidate key (issue 1126)	2026-10-27 02:19:27 +01:00
jschoubben	82f10c3bc9	Let frombus and the composer compose with a given placement and compare a node's compositions with what it runs, so a placement candidate can be answered and checked (issue 1126)	2026-10-27 02:12:11 +01:00
jschoubben	7e99c354ac	Give a catalogue pull request's placement a candidate state and each node an answer in its own have, so a placement change is checked by the nodes it places before it merges (issue 1126)	2026-10-27 02:07:47 +01:00
jschoubben	8e81d87610	Let a replicated mesh seat be held on several nodes in CheckPlacements, so the seed of today's placement is not refused (issue 1126)	2026-10-27 02:04:01 +01:00
jschoubben	a2759ec92e	Merge main into fix/1901-failure-contract: the capacity tests stay one function, so the SDK's test count does not grow (issue 1901)	2026-10-27 00:39:10 +01:00
mesh-tools	f178323b57	Merge pull request 'The mesh-vault seat promises own, the verb L2 gave the vault (issue 1126)' (#103) from fix/1126-vault-seat-own into main	2026-10-26 22:00:44 +00:00
jschoubben	e78e881ecb	The vault's seat promises own, which L2's vault serves and its claim names, so the controller's catalogue check passes (issue 1126) ... mesh-catalog's mesh-vault claims its seat serving own (a machine's node-engine asks its own machine's secrets and pair credentials sealed to its stated key), and buscompose already grants that call to node principals (AsksItsOwnSecrets, VaultOwn); only the seat's verb list lacked it, so a claim naming it was refused.	2026-10-26 22:38:58 +01:00
jschoubben	68d65e6bbf	Merge remote-tracking branch 'origin/main' into fix/delivery-records-true	2026-10-26 22:19:13 +01:00
jschoubben	b4310dfb8e	Merge remote-tracking branch 'origin/main' into fix/delivery-records-true	2026-10-26 22:04:42 +01:00
jschoubben	5f45175ed0	Merge remote-tracking branch 'origin/main' into feat/1126-nodes-compose	2026-10-26 21:56:47 +01:00
jschoubben	805b4d9a35	Merge main into fix/capacity-follows-cpu-share: the build modules' binary refusal (sdk #99) beside the capacity work	2026-10-26 21:26:58 +01:00
jschoubben	d00dac140b	A build module takes asks only within its node's build hours ... The operator, 2026-10-26 21:18: g14 builds only from 18:00 to 06:00. A build-hours setting names a window per node in its local time (crossing midnight allowed, absent = any hour); outside it the capacity judged by is 0, running steps finish, and the puller wakes on one timer at the next edge. The change is said in the log and in capacity.<node> with the window and when it opens.	2026-10-26 21:21:37 +01:00
jschoubben	e44cbaf57f	A module with no floor holds no head back; a merge among its changes reads not yet on the machines (review of issue 1280, ADR 0556 clause 2)	2026-10-26 21:12:48 +01:00
jschoubben	1f70c4c0aa	A settle ask's group begins with a colon, which no branch name holds, so a branch named settle/... still merges on its Approve (review of issue 1280)	2026-10-26 21:12:31 +01:00
jschoubben	5ecda46124	A settle ask's group and the act its options bind, shared by the gate and the teller (ADR 0556 clause 5)	2026-10-26 21:12:31 +01:00
jschoubben	aa8e9afc7c	A module's floor counts every running have, healthy or not; health stays in its words (ADR 0556 clause 2, insight)	2026-10-26 21:12:31 +01:00
jschoubben	54a8afac73	The view's reach carries the reached head and each change's source revision; nothing records a merge as delivered (ADR 0556 v8)	2026-10-26 21:12:31 +01:00
jschoubben	43de3c937d	Layouts of the indexer's taken and the view's reach, and the delivery seat's settle verb, so whether a merge is on the machines can be derived (issue 1280, ADR 0556)	2026-10-26 21:12:31 +01:00
jschoubben	dd9d9d5b5f	Compare haves with SameHave in the round-trip tests, now that a have carries a list (issue 1126)	2026-10-26 20:20:12 +01:00
jschoubben	2c0ab3a592	A have carries the values a self-composing node's running composition holds sealed to its key, so its composer reuses them after a restart (review of L2, round 2; issue 1126, ADR 0547 §3)	2026-10-26 20:19:54 +01:00
jschoubben	47a66e3c0d	Take a crashed file's cause only from what the run wrote after the last test, give a subtest's panic to that subtest, and keep the SDK's test count (issue 1901, review round 1)	2026-10-26 20:17:42 +01:00
jschoubben	3968849b1b	Review of L2: the export is a placement file at its version with its modules (S1); a node asks the vault only when a module placed on it declares an own secret, so one with none composes whether or not the vault answers (H8's failure) (issue 1126)	2026-10-26 20:08:32 +01:00
jschoubben	02f50bd9d6	A build seat's capacity follows its node's build CPU, and a running ask says its phases ... Since the build CPU cap (issue 1806) shanks' mesh-build-go kept capacity 3 inside a 12-core slice: three full checks got about 4 cores each and ran past the 30-minute step bound (issue 1890). The puller now judges by min(configured, floor(slice quota cores / cores-per-step)), the quota read live from its cgroup, says it on change and writes capacity.<node> to the pauses state. A run's phases (fetch and merge, digest, tests) are logged with the ask id and written to its running step key; Asker.Wait hands every step value to a WithStepSeen hook.	2026-10-26 19:52:54 +01:00
jschoubben	81ec7bd7de	Drop the failure contract's unused version constant: a result names its build module with By (issue 1901)	2026-10-26 19:50:17 +01:00
jschoubben	fe11db9293	MergeInto also names programs a commit of the branch added and a later one removed: the merge commit would keep the blob in history (issue 1577)	2026-10-26 19:47:17 +01:00
jschoubben	e40dd0f56a	One failure contract for a build step's failed test, its parsers and a conformance kit every build module runs (issue 1901) ... Each build module parsed its own test runner's output, so a fix in one never reached the others: a failed node --test run was worded by a passing line of its first file. buildstep.Failure names the test, its file, its cause and its own output; ReadGoTest (moved from mesh-build-go) and ReadTAP fill it; package conformance holds every build module to it with runner output captured with the build nodes' own toolchains.	2026-10-26 19:45:35 +01:00
jschoubben	9713c3023a	Placement carries a settings-form module's config values, which mesh-config does not hold, and the export writes them (issue 1126, ADR 0555 §1): the media modules on one node would compose without them	2026-10-26 19:38:37 +01:00
jschoubben	53c2def1a5	VaultSecretChanged is a variable (its seat is), and gofmt (issue 1126)	2026-10-26 19:25:19 +01:00
jschoubben	f55b34febc	A node composing its own hears the vault's secret-changed, names and generations only (issue 1126, ADR 0547 §2)	2026-10-26 19:25:09 +01:00
jschoubben	944a35d200	A node's record carries the mesh's own certificate as the machine holds it, and frombus composes with the composing node's (issue 1126, ADR 0555 §3)	2026-10-26 19:23:06 +01:00
jschoubben	7d81e8326f	frombus gives the composing node's core credentials as the vault's boxes sealed to it, from the same own secrets (issue 1126, ADR 0349 §16, ADR 0550 §5)	2026-10-26 19:22:58 +01:00
jschoubben	91413de335	compose names the pair credentials a node's composition reads as consumer and provider, and frombus asks them sealed before it composes (issue 1126, ADR 0550 §5)	2026-10-26 19:18:46 +01:00
jschoubben	6447a1c6d4	placement-seed writes each node's first placement file from the controller's export, checked before anything is written, once (issue 1126, ADR 0549 §4, ADR 0555 §6)	2026-10-26 19:17:45 +01:00
jschoubben	4d5f430224	A want the node composes itself says so (Self) and names the build alone; every other want names its composition as before, so no caller of the old form changes (issue 1126, ADR 0547 §2)	2026-10-26 19:13:56 +01:00
jschoubben	dfe3ba9475	frombus exports a node's placement from a composition input, Input's inverse for what a person decides, and the controller's seat declares placement-export (issue 1126, ADR 0555 §6)	2026-10-26 19:11:34 +01:00
jschoubben	f1d7c7377d	frombus reads the composing node's own secrets sealed to it, and node principals may ask the vault's own in their own name (issue 1126, ADR 0550 §5)	2026-10-26 19:03:00 +01:00
jschoubben	22bc4dc8ef	MergeInto names the changed files that are compiled programs, read in the workspace, so a check can refuse build output (issue 1577)	2026-10-26 18:59:35 +01:00
jschoubben	b72de2b75a	A node applying what it composed refuses a composition that stands in for anything its input lacks, the bus's user list alone held out (issue 1126, ADR 0547 §2)	2026-10-26 18:59:05 +01:00
jschoubben	6df0dfe208	Node principals read what they compose their own modules from; the composer copy is held per user to the controller's grants plus exactly these (issue 1126, ADR 0547 §2, ADR 0549 §3)	2026-10-26 18:44:06 +01:00
jschoubben	9532b78724	A node's own want names no composition from the second milestone: the node composes its own (issue 1126, ADR 0547 §2)	2026-10-26 18:41:33 +01:00
jschoubben	e49309d61c	A want names the build alone from the second milestone, and the yes a person gave; a have waits for that yes with its judgement (issue 1126, ADR 0547 §2, §3)	2026-10-26 18:39:46 +01:00
jschoubben	9789c8379a	Node principals read every node's own facts, where its record rides; the composer copy is checked to grant all the controller's grants and only that and the issue 1790 rows more (issue 1126, ADR 0555 §3)	2026-10-26 18:33:36 +01:00
jschoubben	2b0689f654	A node's record rides in its own have key, <node>.node: no bucket, writer or grant of its own, and its key's change is what readers hear (issue 1126, ADR 0555 §3)	2026-10-26 18:29:45 +01:00
jschoubben	5b1e990eb4	The tunnel found at adoption and the names of the hub's peers are kept in the placement; whether the hub took it over and who enrolled under a peer's key are read from placement and records, as the controller reads them (issue 1126, ADR 0555)	2026-10-26 18:26:11 +01:00
jschoubben	a431746c0e	What a person decides of a node lives in its placement file and what the machine observes in its record; two nodes on one address or two hubs are refused (issue 1126, K2)	2026-10-26 18:17:59 +01:00
jschoubben	5db53e738f	Name the catalogue repository whose placement files are read (issue 1126, ADR 0549 §1)	2026-10-26 18:10:25 +01:00
jschoubben	9f7f50de8d	A merged message of the catalogue carries its placement files, so the indexer reads placement at the merge without asking the forge again (issue 1126, ADR 0549 §2)	2026-10-26 18:08:59 +01:00
jschoubben	bdd4c7b875	The judgement of a move is a pure function in mesh-sdk, so a node agent judges what it composed against what it runs (issue 1126, ADR 0547 §3, ADR 0377 §3)	2026-10-26 18:07:20 +01:00
jschoubben	e982072443	frombus fills the composition's input from placement, node records, the indexer's manifests and mesh-config's slice, so one composer serves the node agent, the check and the grants part (issue 1126, ADR 0547 §2, ADR 0549 §3)	2026-10-26 18:06:04 +01:00
jschoubben	146cd858a3	Placement and the node record have one layout in mesh-sdk, so the indexer, the node agents and the composition check read them alike (issue 1126, ADR 0549 §1-§2, ADR 0547 §2)	2026-10-26 18:02:13 +01:00