diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index 87d0dc5c..ecd1b78d 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -269,3 +269,11 @@ Where two preparers disagreed, the chosen one is named. - **H-A-69 (seats developer, 02:38)** How the approval gate knows a module's own first-view tool once the callers env marker goes: by the tool's name, the forms `_first_views` and `_first_view_again` that mesh-sdk's views already serve; no environment marker and no tool runner change. P7 (what exists over a new side channel). +- **H-A-70 (contracts-indexer-bridge developer, 02:40)** `acts` stays everywhere as a declaration: it is what the + catalog graph's kind-5 edge ("B has acted for A") is built from, and H-A-51 orders the pipeline's tiers by that edge. + So the `acts` entries of the seats mesh-catalog (take-in, validate), mesh-wants (place) and the build seats stay, as do + `ActingRule` and `CatalogEntry.acts`; what goes is the hold and its wait: `bound` on the build seats' `acts` and every + reader that waits or holds on an acting part (the builder's bound reader and its re-asks, the assigner's acting holds, + the runner's acting waits), each in its own developer's subtask citing this answer (builder and assigner readers: + the runner-and-assigner developer; the pipeline's: the same; the indexer's edge builders stay unchanged). P7 (the + declaration serves the order; only the hold had no need left); ADR 0682 ยง9.