Answer A-407: a running build with no entry is described for resolving by the entry of the build its want says is being built
This commit is contained in:
@@ -963,3 +963,8 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
2026-11-13, and its candidate carried no parts; the operator, as for A-405; principles 5 and 7) The pipeline's manifest is
|
||||
made to pass the judge, as any module's; its first build is asked of the builder once by hand, the way a run on request
|
||||
asks it, since only a pipeline asks builds and none runs yet.
|
||||
- **A-407** (A-405; principles 7 and 2: the node keeps no manifest of a build that has no entry, and the running event
|
||||
carries only a digest) A running module whose wanted build has no entry is described from the catalog entry of the build
|
||||
its want says is being built (the newest of its first watched branch), read through the seat `mesh-catalog`'s `entry` as
|
||||
any entry: what it provides, claims and requires there stands for the running build, for resolving the node alone. A
|
||||
want that names no newer build leaves the module as today (a name alone), said once.
|
||||
|
||||
Reference in New Issue
Block a user