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 ecd1b78d..a3eb67e6 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 @@ -277,3 +277,10 @@ Where two preparers disagreed, the chosen one is named. 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. +- **H-A-71 (contracts-indexer-bridge developer, 02:49)** (1) The seat mesh-delivery's state `owed` stays in H1: the + bridge's owed path and the client's check read it (P7 removes only what nothing reads); its stale keys of the earlier + model go at the clean state's drop step (ADR 0682 §12), and §764's "owed (the old bucket)" reads so. (2) The call's + kept member gains `branch`, so the forge module can say `merge-called` again after a stop (P3). (3) The step runner's + asker judgement in `mesh-delivery-sdk/steprun` (H-A-41) is the contracts-indexer-bridge developer's subtask, since + that package is mesh-delivery's shared code and it already writes there; the three build modules' wiring stays + mesh-catalog's BUILD-1. The lead's order of work.