Design 47 G: A-459b withdraws A-459 and A-459a; A-462b #652

Merged
mesh-tools merged 1 commits from design/47-G-lead-answers-66 into main 2026-11-17 00:32:53 +00:00
@@ -1445,3 +1445,12 @@ the principle that settles it, cited as "design 47 G A-n".
- **A-457b** (A-457, A-457a; principle 7) The builder's setting `republish-max-versions` goes: it bounded what one
`running` or `manifest-reads-changed` event queued for publish, and A-457 retired that path, so nothing reads it.
A value set for it in the mesh's configuration is left unread and may be removed there. (From the review of A-457a.)
- **A-459b** (withdraws A-459 and A-459a; ADR 0571 §6; principles 7 and 10) Rule 7 reads the node's own composition,
as on main: a node names its composition only after it composed what its wants name, so no node holds a module's
composition at a fingerprint before a want names it, and a per-module, per-fingerprint read would hold every new
build on every placed node. That one module costs only itself is the node-engine's part (A-452, A-461): a node that
composes the rest names its composition, so no module's fault holds the others. (From the review of A-459: four
order-wait tests fail and no placed node moves once the fixtures write compositions as the node-engine does.)
- **A-462b** (A-462a; principle 3) A want a rule holds keeps that rule's words, which say why it does not move; A-462a's
words ("waits for the entry of that fingerprint") are written only on a want no rule holds. (From the review of
A-462.)