diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index aef01a10..73b12bfe 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1851,3 +1851,11 @@ the principle that settles it, cited as "design 47 G A-n". running is never a condition for laying another node's module; the assignment is the mesh's truth of what is placed there. (From the develop of the store fetchers' fix: shanks heard no `running` of `distribution` on novox, so it laid the store's holder name-only and found no store address.) +- **A-461e** (A-461, A-452, narrows A-461b's last sentence; principles 3 and 10) No artifact store address, for any + reason the inputs read without error (no holder found, its holder laid name-only, or its machine not on the private + network), holds only the modules that fetch from the store, each staying on the build it runs with A-452's + "nothing provides" words, and the node composes the rest. A fault reading what finds the store (an input that cannot + be read or decoded) still refuses the node. A trunk build the composer could not get through the seat + `mesh-catalog`'s verb `module` is said with its reason and asked again on the next pass, so a store holder left + name-only by a failed ask is loud and recovers without a restart. (From the review of the store fetchers' fix: the + live case is a name-only holder, which A-461b's "every other fault still refuses the node" would have refused.)