Answer A-243: one composition request per machine; every run input any size

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 534fd88be4
commit 3b309fa61e
1 changed files with 5 additions and 0 deletions
@@ -245,3 +245,8 @@ the principle that settles it, cited as "design 47 G A-n".
  `view_tiers` call for a source revision compares the kept assignment revision whose catalog for that branch is that
  source revision with the revision kept before it. The view keeps a state `waits` (key owner, step, node, module)
  written by its process from every part's `wait-held` and `wait-ended` it consumes, read by its own read tool.
+- **A-243** (corrects A-226's joining; A-237, A-238; principle 7) The composition step runs one request per machine,
+  each carrying that machine's input; no inputs are joined. A-237 holds for every run's input (the assigner's and
+  `mesh-wants`' `input` too): any size, kept with an `-objects` store, answered in chunks. The composition run names
+  no head (A-238); its program is the node-engine fingerprint's entry (repository, commit, directory) with the
+  composer's package.