diff --git a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md index 90979a34..4553867b 100644 --- a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md @@ -602,3 +602,11 @@ The lead's one-line answers to the questions H2's develop and review raise (impl - **H-A-442 (a source-only check says run-started, 01:56)** R11. The runner says run-started for a source-only check as the verb's definition has it (one event for every run); the indexer builds no candidate for a `source.*` member (I6), so nothing downstream takes the run for a module's. P3. +- **H-A-443 (the seat-list verb hands the bytes; a revision's own definitions stay, 01:58)** H-A-441, I6 (2), A. (1) No + tool reads another module's objects (ADR 0596), so the owner serves them: the seat mesh-catalog's `seat-list` is a + chunked read verb (the compose-candidate form, process.CallChunks) answering `digest` and `size`, then the object's + bytes in chunks; D4's row reads so (the object name goes), the indexer's I6 (2) builds it, and the assigner's validate + step and the checker invoke `seat:mesh-catalog.seat-list` and fill Request.Seats from the bytes. (2) The object replaces + the trunk fallback only: a revision that names its own definitions (a candidate judged with the group's altered + definitions) keeps them, and the request's `seat-list` then names the sha256 of those bytes in the same form, so the + digest always says which bytes judged. P3, ADR 0596.