Answer A-484a: the running statement's manifest is the second source; a composition answers only kept data

This commit is contained in:
2026-11-18 00:47:21 +01:00
parent 2c95a12b8f
commit e69b81b8ea
@@ -1961,3 +1961,9 @@ the principle that settles it, cited as "design 47 G A-n".
the same place, also when its want's build has no composition (principle 4). (From the feh proof, 2026-11-17/18: four
steps in a row held feh 0.1.8 on g14 because its running build, and about 70 others there, were placed before G and
have no entry; each was given its own fallback.)
- **A-484a** (A-484, A-480a; principles 2 and 7) A composition holds no manifest: it answers only whether the build it
runs keeps data on the bus. So the one place answers the manifest of the build a module runs, in this order: the
entry of the running build; else the manifest its running statement names, when this node holds it; else the trunk
manifest through the seat `mesh-catalog`'s verb `module`. What it keeps on the bus is read from the manifest it
answers, or, when it answers none, from the composition this node runs of that build (A-483). (From the develop of
A-484.)