Answer A-316: a candidate carries the parts of the modules it adds

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 22:45:27 +01:00
parent aef65c2f1e
commit f6cb279eea
1 changed files with 6 additions and 0 deletions
@@ -536,3 +536,9 @@ the principle that settles it, cited as "design 47 G A-n".
  check gives the test. Each fetched build is started the way every module is, by the node-engine's own apply of a
  want on the test's bus, under the module's own account; the test starts no bare process. Where the seat does not
  answer, the test fails, saying which build it could not fetch and why; it never skips.
+- **A-316** (§379, §421, §628, A-312; principles 2 and 7) A node-engine composes a candidate only from what its asker
+  gives it, as it composes a want. The assigner's candidate `<proposal>.<node>` gains `added`: by module, for each
+  module the candidate adds to that node without a want there, the `version` and `parts` the want it would write
+  carries, in the want's own forms and made by the same code. The node-engine's shadow builds such a module from that
+  entry and its `added` parts; a module with artifacts the candidate gives no parts is held, saying so. Nothing reads
+  the builder's states or asks the registry for it.