Design 47 H: lead answers H-A-65 to H-A-68 to H1's developers #741

Merged
mesh-tools merged 3 commits from design/47-H1-answers-3 into main 2026-11-20 01:35:32 +00:00
@@ -248,3 +248,21 @@ Where two preparers disagreed, the chosen one is named.
existing output changes; a subtask of the contracts-indexer-bridge developer in `mesh-delivery-sdk/seatgen`), and the
node-engine definition gains the enum `ManifestReadWord` with that value. P9 (every reader takes it from the generated
package), P7.
- **H-A-65 (tool runner developer, 02:33)** How the setting `call-timeout` reaches the tool runner: not in H1. The
node-engine composes the tool runner's unit as a special case (two environment variables, no config file), so the
setting's path is the generic manifest `config` with its file resource, built in H4 when that special case goes
(principle 7, no module special-cased in shared code). In H1 the runner's own bound is a constant of 30 seconds and the
per-verb `timeout` carries every real need (`merge-pull` 120); the manifest declares no setting it does not read
(principle 3). Rules-are-weighed: principle 11 bent for one release, said to the operator.
- **H-A-66 (seats developer, 02:36)** H-A-41's set is the whole of it: mesh-sdk's `go/callers.go` (`stdio.Callers`,
`VerbCallers`, `ParseVerbCallers`, `ConfiguredVerbCallers`, `HoldVerbCallers`), the `callers` parameter of
`seatlist.NewPart`, `Tools` and `Refusal`, of `views.FirstViewTool`, `ParseCallers`, `Refusal` and `CallersEnv`, and
`approval.ViewCallersPrefix` go in H1, as the sdk developer's subtask `sdk-holder-callers-gone`; every gated first-view
tool and seat-list tool is open to every caller. The holders' call sites in mesh-delivery and mesh-catalog are their
developers' subtasks, from the signatures the sdk developer reports (the lead relays them). P6, P7 (code that gates
callers protects nothing once every account may call every verb); ADR 0682 §10.
- **H-A-67 (node-engine developer, 02:37)** The node-engine seat's `Wait.step` enum gains `placing` (the seats developer
in mesh-contracts, with the sdk copy); the hold of a higher rank behind a lower one is said with it. P8.
- **H-A-68 (node-engine developer, 02:37)** A revert is a want with no `pipeline` and no `rank` (a placement's `build`,
H-A-37) naming a fingerprint other than the one running; the applied record keeps no history for it. "Read from the
applied record" in H-A-59 reads so: the running fingerprint is what it compares with. P7.