A-316: the assigner's seat defines the two properties itself, held to the want's by a fixture

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md

@@ -539,6 +539,7 @@ the principle that settles it, cited as "design 47 G A-n".
 - **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
+  carries, in the same wire forms (the seat format reuses nothing across repositories, so the assigner's seat
+  defines the two properties itself and a fixture holds them to the want's), made by the same code that writes wants. 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.