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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
The running build's entry stays held (kept in the composition state) while the node runs it, though the catalog half dropped it; the agent no longer tells the composer it waits for a composition it holds, and the composer hands again when the entry answers.
Builds: design 47 G §296, §297, A-113, §614
A want of a released build names the module's version and no parts. Each artifact of the build's entry is
resolved at that version through the verb versions of its kind's registry seat: oci-artifact-registry for a
bundle or an archive, container-image-registry for an image, under <module>/<artifact> or a package's own
name. An upstream copy, which is not numbered, takes the digest its manifest pins. partsMissing, buildOf and
KeptBuildOf (and the shadow's added modules) read those digests; a want with parts is read as before.
A lookup that fails is said in the journal, naming the module, the version and the seat, and holds the module
whole: nothing of it is composed. It is asked again after a minute. The manifest invokes both verbs.
Builds: design 47 G A-430, A-430a; lead answer A-430b
The composer's Build is made from the catalog half's entry it holds and the parts of the want that names it (buildOf); the
inputs of the indexer's modules and the builder's builds, takeBuildDone, takeModule and the builder read are gone, and mesh-host
names no BuilderBuildsBucket. The shadow takes the entries of the builds it composes from (askBuildsEntries), builds a module a
candidate adds from its entry and the candidate's `added` parts (A-316), and holds, with the reason, a module whose entry
has no part given, whose fingerprint the verb module does not give, or for which it errors (A-312). Its composer is given the
entry call as the node's own is. Rows: a built module added with and without parts, the verb module answering no fingerprint
and erroring.
Builds: design 47 G §421, §628, A-308, A-312, A-316
Reading the catalog half by fingerprint, the node-engine no longer reads the builder's builds, so #224's refused key was
never written there and a reader waited on a build that will never be done. The engine now hears the builder's
build.ended stream, read whole at start then followed (as the assigner hears it); the last trunk end of a placed module
that ended failed is written as the refused key with the event's words, a later done end deletes it, an end naming a
branch moves nothing. The manifest consumes mesh-delivery-builder.build.ended.**.
Builds: design 47 G A-293 (with §421, §628), ADR 0593 §6, issue 1966 U1/U8
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
Brings mesh-host #224 (issue 1966): newestFPs returns a placed module whose
newest build failed, composedValues writes its refused key at that fingerprint,
takeBuildDone starts the pass on a failed build. Conflict in newestFPs settled
by keeping G's by-entries branch first (design 47 G §421, §628: the node reads
neither the indexer's modules nor the builder's builds; it returns no failed),
and main's failed-build path in the other.
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
mesh/check checking 8e993c759a5c on df1412081bed | novox/mesh-host#224 in group fix/1966-unpublished-placed-module
The node-engine writes a refused key, with the build's own error, at the indexer's
fingerprint in composed-<node> for a placed module whose newest build the builder
holds failed; a build queued or running stays unpublished (U1). A failed build of a
placed module's newest fingerprint also moves the pass (takeBuildDone), so the key is
written when it lands (U8).
Builds: design 47 fix-unpublished-placed-module U1, U8, ADR 0593 §6
The delivery repository's contracts and SDK live under modules/ as
mesh-delivery-contracts and mesh-delivery-sdk, their Go module paths
renamed to match the folders (the TypeScript names already did), and
every importer in mesh-delivery, mesh-catalog, mesh-host, mesh-tools
and mesh-sdk follows in the same group: a design as it should be, one
path per module, checked by the group's check building every importer.
Builds: design 47 G §427, §88
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h