Answer A-75: mesh-issues' pipeline rows in its delivery line

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 23:03:39 +01:00
parent 0fe2118105
commit 8e87bdc148
1 changed files with 4 additions and 0 deletions
@@ -283,3 +283,7 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  `operator-channel`: its manifest `uses` that seat, and the bucket is formed from the seat's holder on the seat list
  and the contract's `StateAsks`, never a module's name in code; the teller's and the node-engine's `messenger_asks`
  constant goes the same way in their own change.
+- **A-75** (§654, §610; principle 7, and who may do what is no question) mesh-issues shows the pipeline rows where it
+  already shows a delivery: its `DeliveryLine` gains `pipelines`, one row per module with its steps, `no run` where the
+  runner's list answers none. A runner verb's old callers list does not refuse a module: from G no verb names its
+  callers (§610), so the class's default holds.