Answer A-294: mesh-wants' step keeps no token; step-progress names the caller its definition lists

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 18:54:41 +01:00
parent 7247b92fd6
commit 12c9c1efcf
1 changed files with 4 additions and 0 deletions
@@ -443,3 +443,7 @@ the principle that settles it, cited as "design 47 G A-n".
  writes the refused key `<node>.<module>.<fp>` with the event's words, a later done end of the module (at any
  fingerprint) deletes the refused key such an end wrote, so the state never says refused for a done build, and an
  end naming a branch moves nothing.
+- **A-294** (corrects A-267; §600, A-170; principle 7, the seat definition is the one source) The seats mesh-wants and
+  mesh-builds are not build seats: their accepted kind `step` stays without a token (not `by-caller`), and the
+  composition step's step-progress names its asker as the one caller its seat's definition lists, read from the seat
+  list; only the three build seats carry the asking seat's name as a token.