Commit Graph
1297 Commits
Author SHA1 Message Date
jschoubben d217056cf7 H-A-177: move a data module without its restore point where no recovery holder is placed
The node-engine held every data-holding module's take-in for good: it asked
the seat mesh-recovery for the restore point, and nothing answers because
no holder of the seat is placed on the mesh (H §456). It now asks only where
the assigner's placements it holds name a holder (and while they are not
read yet); where none is placed it moves the module without a point and
raises the finding restore-point-missing (warning, scope machine, id the
module), cleared at the module's next take-in that takes its point. A holder
placed that does not answer still holds the move.

Builds: design 47 H §456, H-A-177
2026-11-20 18:56:43 +01:00
mesh-tools b877d36f6f Merge pull request 'Design 47 H1: the node-engine forgets a resolution whose fetch the store refused (H-A-146, H-A-150)' (#240) from fix/47-H1-engine-forgets-failed-resolution into main 2026-11-20 15:47:41 +00:00
jschoubben 07a27bcd40 H-A-150: hold the apply's forget on bytes not of the digest with a test
The apply's fetch tells the composer of bytes that are not of the declared
digest (fetch_first.go), but no test held it: with that call disabled every
test of internal/apply passed. TestAStoreThatStaysAwayCostsOneBoundedWait now
has a store that serves other bytes to two modules from one source, and the
composer is told exactly once, with the declared digest.

Builds: design 47 H H-A-150
2026-11-20 16:45:59 +01:00
jschoubben 132b767043 H-A-150: forget only on the store's own answer, and on the apply's fetch too
A fetch nothing answered for (a bus or store that did not answer, a gateway
saying the store is away) proves nothing about the digest, so it is tried
again as before and the module is not held for it; only an answer of the
store's (a 404, bytes not of the digest) forgets the resolution. The apply's
fetch of a bundle meets the same wrong digest as the take-in's, so it tells
the composer too (apply.WithFetchFailed, set in the node agent's apply).

Builds: design 47 H H-A-150, H-A-146, G A-430a
2026-11-20 16:35:42 +01:00
jschoubben dc95fb5673 H-A-146: forget a resolution whose fetch failed, so versions is asked again
The engine kept a want's version resolved to a digest for its process's life
even when the artifact store's fetch of that digest failed (404, or bytes not
of the digest), so a fix of the store's answer never reached the node without
a restart. A failed fetch now forgets every resolution naming that digest, says
"resolution of <module> <version> forgotten: <why>" in the journal and holds
the module; the seats' verb versions is asked again at the module's next want,
at the next compose by hand, and after resolveAgain (the bound a failed lookup
already has). A resolution whose fetch succeeded is kept.

Builds: design 47 H H-A-146, G A-430a
2026-11-20 16:31:20 +01:00
mesh-tools 0b388fa675 Merge pull request 'Design 47 H1: the node-engine composes its wants from the bus (want fields, version, apply-order)' (#239) from feat/47-H1-node-engine into main 2026-11-20 07:15:11 +00:00
jschoubben 39e16689fa MH-0: an entry whose ask failed is asked again, at most entry-asks times, then unanswered
The node-engine consumes the entries client's asking again (H-A-60, H-A-110): the setting entry-asks (default 5; module.json
config and file resource, read at the engine's start) goes to Entries.Asks; Entries.AskAgain is called at each link's start and
on each catalog-revision the composer hears (the shadow's cache too); the finding entry-unanswered joins the engine's finding
kinds, written with a journal line when an entry ends unanswered and cleared when it is answered or no longer wanted; the
shadow's wait and the have's hold end on it instead of waiting without bound.

Builds: design 47 H, H-A-60, H-A-110

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
2026-11-20 04:25:00 +01:00
jschoubben e4d098c4b9 MH-7: the node-engine reads a module of a catalog revision as accepted: no verdict is read
The seat mesh-catalog keeps no state verdicts (H-A-79): frombus taken, the composer's parse and the composer's
reading of a candidate drop the verdict branch and decode the manifest alone, a module in a catalog revision being
accepted by being there; the composer no longer reads the request field Case.Verdicts (H-A-112). Tests that held a
module by a verdict hold it by the decoder, or go.

Builds: design 47 H, H-A-79, H-A-111, H-A-112

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
2026-11-20 04:24:53 +01:00
jschoubben dd2b3a16df MH-2b: the node-engine reads the want by the real contract: composed, kept-on and newest go
A want carries no composed digest, no keeping node and no newest build (design 47 H 750,
H-A-37): the agent takes the digest from the composition the node made for the want's
build, the shadow's resolution around a missing entry (A-405) and KeptBuildOf's keeping node
go, and the artifact is fetched from the store. Tests of the removed behaviour go.

Builds: design 47 H §750; H-A-37

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
2026-11-20 03:09:22 +01:00
jschoubben ee017fe306 MH-6: the test budget: three pairs of tests covering one rule twice become subtests
Unit test functions: 1,719 before H1, 1,717 after (three fewer by the merges, one added for the
claims read); integration tests: 10 before, 11 after (budget 50). The module stays over the
unit budget of 500.

Builds: design 47 H §774

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
2026-11-20 02:41:48 +01:00
jschoubben 6e4d0c7f47 MH-5: the whole test of the apply order against a real bus
A want of rank 2 whose composition is made first is held in a wait of step placing on the
module of rank 1 of its pipeline; rank 1 is applied first, rank 2 after it, and the wait ends.

Builds: design 47 H §771, §774; H-A-59

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
2026-11-20 02:40:03 +01:00
jschoubben ad69a53032 MH-4: the verb apply-order of the seat node-engine answers the order of the applies
One row per unapplied changed want: module, pipeline, rank, position, why, waits.
Served beside process-builds and claimed in module.json.

Builds: design 47 H §771; H-A-46

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
2026-11-20 02:38:56 +01:00
jschoubben 949b782a1e MH-3: the apply order by rank, the revert, the backup holder and the bus module first, the engine's own module last
settle applies the changed wants in the order of design 47 H 771: the node's own composition,
a reverted module, the holder of node-backup and the bus module (by the claims of the manifests
the composer holds), each pipeline's wants by rank (older source first), the rest by name, the
engine's own module last. A want of a higher rank waits on this machine alone for the lower
ranks of its pipeline, held in its have as a wait of step placing and judged again at the next
settle. The want's pipeline and rank are the mesh-delivery contract's stand-in until its commit.

Builds: design 47 H §771; H-A-46, H-A-59, H-A-67, H-A-68

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
2026-11-20 02:37:59 +01:00
jschoubben d2b6ecdf0e MH-1: the node-engine states that it reads a want by version; want-parts goes
The record's capabilities no longer hold want-parts; manifest-reads holds the word
want:version, stated at the first reading and said by manifest-reads-changed.

Builds: design 47 H §772, §764; H-A-45

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
2026-11-20 02:33:02 +01:00
jschoubben ea25a8389d MH-2: a want is read by its version alone; the parts check and parts-differ go
The node-engine no longer reads a want's parts: the parts check (G 524) and its hold
parts-differ are removed, the digests of a build are resolved through the registry
seats from the want's version, and a candidate's added module is resolved from its
version alone.

Builds: design 47 H §750, §764; H-A-37, H-A-38

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
2026-11-20 02:31:13 +01:00
mesh-tools 3e17fc939d Merge pull request 'Node-engine asks a missing trunk build again on a backoff or a catalog-revision (A-487a)' (#238) from fix/trunk-ask-backoff into main 2026-11-19 10:49:10 +00:00
jschoubben 85d1707e82 selfcompose: the trunk-ask backoff test is a subtest of an existing test, no function added
Builds: design 47 G-22 A-487a, the test budget (module total back to main's count)
2026-11-19 01:24:02 +01:00
jschoubben cb6cd9d996 selfcompose: hear catalog-revision on the contract's subject, consume it in the manifest, one test
Subscribe to meshcatalog.SubjectCatalogRevisionAll (no string of its own); module.json consumes
mesh-catalog.catalog-revision so the node account is granted it; the two new tests are folded into
TestTrunkAskBackoffAndCatalogRevision and wait on channels, not time.

Builds: design 47 G-22 A-487a, A-487c, principle 3
2026-11-19 01:18:38 +01:00
jschoubben 2057c9d304 selfcompose: a refused catalog-revision subscription is said once and tried again, never refuses Watch
The subscription is a wake-up; the backoff bounds the asks without it. The refusal is said with its subject and error
(principle 3), the composer goes on, and the subscription is tried again on laterAgain's steps until it holds.

Builds: design 47 G-22 A-487a, principle 3
2026-11-19 00:59:17 +01:00
jschoubben 6ac8952541 selfcompose: ask a trunk build the catalog gave none of again on a backoff or a catalog-revision, not at every pass
A trunk build answered none waits laterAgain's step for its module (5 s growing to 5 min); the seat mesh-catalog's
event catalog-revision, heard through Env.Hear, ends the wait of every module at once; an answer starts the steps
again. A pass is woken at the step's end.

Builds: design 47 G-22 A-487a, A-461e, G-12 line 317
2026-11-19 00:57:21 +01:00
mesh-tools 6e89a5defd Merge pull request 'resolution: an own secret owned by the operator account or root (ADR 0680 §4 test rows)' (#237) from fix/adr0680-own-secret-owner-rows into main 2026-11-18 01:18:52 +00:00
jschoubben 4b11f66b4b resolution: an own secret's owner may be the operator account or root, as rows of the owner table (ADR 0680)
Builds: ADR 0680 §1, §4
2026-11-18 02:11:40 +01:00
mesh-tools 0439af3649 Merge pull request 'A-480..A-484a: a held provider's provides, the one place for a running build's manifest, the composition tool's deadlock fix' (#236) from fix/a480-held-provider-provides into main 2026-11-18 01:11:04 +00:00
jschoubben 5cc26e2659 selfcompose: the one place says its source at every caller, reads the have's build, answers HoldsData; the tool composition reads it outside the agent's lock (A-484, A-482)
Builds: design 47 G A-484, A-484a, A-482
2026-11-18 01:02:10 +01:00
jschoubben 91dc064f92 selfcompose: the running statement's manifest is the second source of the one place; a composition answers only whether the build keeps data (A-484a)
Builds: design 47 G A-484a, A-484
2026-11-18 00:49:53 +01:00
jschoubben 7b6468e2bb selfcompose: the manifest of the build a module runs here is answered in one place; every step reads it there (A-484)
Entry of the running build, else the composition this node runs of it, else the module's trunk manifest through the seat mesh-catalog's verb module;
said once per module and source; words naming the three where none answers. Read there: a held module's offer (frombus Scope.RunningManifest),
FormChanges (A-483), the store holder and the stand of a running module without an entry (A-461d, A-480a), and the tool composition.

Builds: design 47 G A-484, A-480, A-480a, A-483, A-461d, A-482
2026-11-18 00:46:49 +01:00
jschoubben 0cc1728a04 agent: a held have is judged again at a start from its wait's reason, not from its detail's opening words (A-453, §541)
Builds: design 47 G A-453, §541, A-484
2026-11-18 00:34:36 +01:00
jschoubben d1768241dc selfcompose: a running build with no entry keeps what its running composition keeps; with no data on either side the move goes on (A-483)
Builds: design 47 G A-483
2026-11-18 00:23:46 +01:00
jschoubben cdd8bd3cba selfcompose: what is read decides the trunk build's stand: the running event's manifest held, a running composition's build read as ranOf reads it (A-480a, A-482)
Builds: design 47 G A-480a, A-482
2026-11-17 23:58:13 +01:00
jschoubben 121a8090b3 composer: a take-in's templates digest is no difference between two manifests (A-481a)
Builds: design 47 G A-481a
2026-11-17 23:57:16 +01:00
jschoubben ba9d4787f9 selfcompose: a module counts as running here only when heard, run by the agent or its have says running or held; the trunk build stands only where no manifest is named (A-482, A-480a)
Both review findings of 7bfeb466 and 179a4a64 sit in runsWithoutEntry and are one change.

Builds: design 47 G A-482, A-480a
2026-11-17 23:46:03 +01:00
jschoubben 87cfae48b2 agent: the parts check counts the templates archives a composition was rendered from as fetched (A-481, A-481a)
compose fills Composed.Templates from the resolved manifest's TemplatesDigest; partsDifference adds them to the digests fetched.

Builds: design 47 G A-481, A-481a
2026-11-17 23:44:15 +01:00
jschoubben 179a4a6402 selfcompose: a module built by hand, with no running event, is held as running; its trunk build is asked (A-480a)
Builds: design 47 G A-480a (G-22-lead-answers-2.md)
2026-11-17 23:16:33 +01:00
jschoubben 7bfeb466bf selfcompose: a module that runs with no entry of its wanted or running build counts what its trunk build provides (A-480a)
Builds: design 47 G A-480a (G-22-lead-answers-2.md)
2026-11-17 23:09:15 +01:00
jschoubben e7803f8943 frombus: the A-480 rows join the held-rows test, no new test function
Builds: design 47 G A-480 (G-22-lead-answers-2.md)
2026-11-17 23:01:09 +01:00
jschoubben baeb87d195 frombus: a held module still provides what its running build provides (A-480)
A module the node holds keeps running what it runs, so a module that requires what it provides is no longer held for
"nothing provides": the held offer's provisions are the running composition's build's manifest, else the manifest the
module's running event names.

Builds: design 47 G A-480 (G-22-lead-answers-2.md)
2026-11-17 22:58:11 +01:00
jschoubben 9172eccbc4 selfcompose: only what the node needs of another node's placement is asked, beside the pass
The trunk build is asked, and a placed module laid, only for the store's
holder (a store seat's holding on that node) and the providers this node's
modules are bound to; never every module placed elsewhere. The asks run beside
the pass, three at a time, and an answer asks a pass; a module that waits is
only the one needing that address.

Builds: design 47 G-22 A-461, A-461d, A-461e
2026-11-17 16:52:28 +01:00
jschoubben 07ea73bd64 selfcompose: a stopped or build-less placed module is laid from its placement; an unobtained trunk build is asked again
lacksEntry holds for a stopped run and for one naming no build, and the loop
for another node's placed modules lays every one not yet laid where it holds.
A trunk build askTrunkBuilds could not get is said with its reason and asked
again on the next pass.

Builds: design 47 G-22 A-461d, A-461e
2026-11-17 16:12:51 +01:00
jschoubben d57e2325f6 composer: a store fetcher left out is held with its words, so its handed composition stays
Declared.Held carries the modules composeWithoutStoreFetchers leaves out
(A-452: each stays on the build it runs). The store-address comment and code
say A-461e: no address read without error holds only the fetchers, a fault
reading the inputs still refuses the node.

Builds: design 47 G-22 A-452, A-461, A-461e
2026-11-17 16:11:59 +01:00
jschoubben 43c812e98e selfcompose: a module placed on another node and not heard running is laid from its placed or trunk build
Being heard running is no condition: such a module counts as one whose
running build has no entry (wantedBuilds, askTrunkBuilds, layModules,
lacksEntry), so the store holder is found from the build its placement names or
its trunk build.

Builds: design 47 G-22 A-461d, A-461b
2026-11-17 16:06:01 +01:00
jschoubben e3d994fde1 composer: a module that fetches from an artifact store no node reaches waits alone, never the node
Typed resolution.NoStoreError from artifactsInto (image, source, tools bundle,
runtime program, templates archive), laid on its module by
composeWithoutStoreFetchers with A-452's "nothing provides" words and composed
again, instead of a whole-node refusal. Replaces storeHeld and
modulesNeedingTheStore, whose shape list missed bundles and held stand-ins.

Builds: design 47 G-22 A-452, A-461, A-461b, A-459b
2026-11-17 16:03:18 +01:00
mesh-tools eb89cb7da3 Merge pull request 'G-24: the node-engine's composer names the modules it blames' (#235) from fix/47-G-composer-blames into main 2026-11-17 12:15:37 +00:00
jschoubben ed7cefb5d8 composer: the search for culprits goes on past a hold that changes the problem (G-24 review r2)
A hold that changes the problem but leaves the machine not composing keeps that module held and blamed,
and the search goes on against the retry's problem within the same blame_tries, until the machine
composes or no hold changes it: every module the change refuses is blamed, never only the first.

Builds: design 47 G §721, §722, A-470c, A-470v
2026-11-17 13:10:51 +01:00
jschoubben f21b8c202d composer: a build that can never be made is blamed after the held composition is judged (G-24 H3 review r1)
The held composition's own blames and its search come first; the module whose build can never be made is
then blamed beside them. A held composition that still fails and blames nobody stays on the node's own
account, so the module is not blamed in its place.

Builds: design 47 G §721, §722, A-470j, A-470k
2026-11-17 13:05:38 +01:00
jschoubben b4bf772de4 composer: one search for culprits, inside the node-engine's composition, bounded by blame_tries (G-24 H2 review r1)
ComposeSent no longer runs the node-engine's own culprit search (fixed at eight modules), and the composer's
own loop, which reran that search at every try, is gone: ComposeSent holds the case's changed modules on the
machine one at a time, one composition each, at most blame_tries, and blames the first whose hold ends the
problem; past the bound the untried are named. Without blame_tries there is no search. A module the node
holds composing without the change is held as there, and two owners of one path are blamed outside the search.

Builds: design 47 G §721, A-468i, A-468l, A-469j, A-469k, A-470c
2026-11-17 13:03:15 +01:00
jschoubben c5f76cb974 composer: a build that can never be made is blamed, not a reason to judge no machine (G-24 H3)
A module awaited on a machine whose revision gives it no fingerprint (the case's none) is held as its
node-engine holds it, the machine judged from that composition, and the module blamed with the revision's
none words, so only its own pipelines fail. An awaited build with a fingerprint keeps the machine not judged.

Builds: design 47 G §721, §722, A-470j, A-470k
2026-11-17 12:04:20 +01:00
jschoubben 8700aabba3 composer: a machine that fails with no module held is searched for its culprit, bounded by blame_tries (G-24 H2)
The composer program has no settings, so the assigner bounds the search through the request: only the candidate's
changed modules placed on the machine are held, one at a time, the search ending at the first whose hold ends the
problem; past the bound the untried are named. A request with no blame_tries gets no search.

Builds: design 47 G §721, §733; A-468h, A-468i, A-469i, A-469j, A-469k
2026-11-17 11:21:49 +01:00
jschoubben 06781d4dbc composer: a machine's verdict names the modules it blames (G-24 H1)
The assigner fails only the composition steps of the modules a machine blames, so the composer names them: the modules
the change refuses that the node held neither in its read nor composing without the change, answered structured by
ComposeSent, and both owners of a path two modules own, from the resolution's pairs. Blamed is always written, so a
verdict blaming none is told from an old composer's. The two request-file tests are one, for the test budget.

Builds: design 47 G §721, §733; A-468h, A-468l, A-469h, A-469j
2026-11-17 11:19:54 +01:00
mesh-tools d0b208b668 Merge pull request 'node-engine: the golden node grant holds every verb the manifest invokes (A-461c)' (#234) from fix/47-G-node-engine-integration into main 2026-11-17 08:49:22 +00:00
jschoubben 85ad1eef74 nodegrant: the A-461c check of the golden grant runs in an existing test, no test added (test budget)
Builds: design 47 G-22 A-461c
2026-11-17 09:46:55 +01:00