Answer A-459a: rule 7 hears composed per module and fingerprint from the node-engine's events

This commit is contained in:
2026-11-17 01:09:38 +01:00
parent 242bae0d0c
commit fc5ec32b90
@@ -1395,3 +1395,8 @@ the principle that settles it, cited as "design 47 G A-n".
the want says it waits for the entry. (Survey 2026-11-17: 40 to 80 modules per machine on wants from before G with
no version or parts, `entry-missing` or "want names no digest", and a want was rewritten only after a passed
pipeline, which waited on A-458.)
- **A-459a** (A-459; principles 1, 10 and 3) Rule 7 learns "composed" per module from the node-engine's `composed`
for `<node>.<module>.<fp>` (its digest a composition, a refusal not composed), heard on the node-engine's per-node
`mesh-host.composed` events the assigner follows in its pass as it follows the haves, never by reading the
node-engine's bucket; the module's own have is not the source, since none names a fingerprint before its want does.
(From the develop of A-459: `composed(node, module, fp)` read only `<node>.node`.)