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 new file mode 100644 index 00000000..9d8a676b --- /dev/null +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -0,0 +1,41 @@ +--- +layer: to-be +status: in-progress +design: 47 +milestone: H +updated: 2026-11-20 +decisions: + - "ADR 0682" +--- +# 47, milestone H — the lead's answers + +The lead's one-line answers to the questions the design writer and the builders could not answer from the records, +each tested against the principles (`00-META/principles.md`) and naming the one that settles it (implement-the-design). +A question no principle settles goes to the operator or to a record; it is marked so here. + +## From the design writer (2026-11-20 01:36 CET) + +- **H-A-1 A member refused after every member was judged** (a forge failure between the judgement and the last merge): + the forge module says the members that landed, marks the call `refused` and raises the finding `merge-partial`; + the landed members are taken in as one source revision, so what landed is delivered and what did not is loud. + Principle 3. +- **H-A-2 The delivery order once the want holds for nothing**: the runner's `pipeline-ended` carries its movers in + ADR 0666 §14's delivery order, and the node-engine applies one pipeline's wants on its machine in that order + (A-478b's order on one machine). The order travels in the event; no part reads another part's state for it. + Principles 1 and 9. +- **H-A-3 A `required` step whose run ends "nothing to run"** counts as passed for the want, as `bypass` does: a hold + with nothing behind it protects nothing. Principle 7. A clause of ADR 0682 says it (asked of the record writer, 01:38). +- **H-A-4 Reads whose owner says no event today** (the provisioner's provisions, the vault's bus accounts and node + logins, the enrolment module's enrolments, the grants part's user list): each owner says one change event and the + readers consume it, in milestone H4b; until then the read stands and is named a leftover in the gap table. + Principle 1 (ADR 0596). +- **H-A-5 A revert against the whole want rule**: a return to an earlier build stays one value in the placement, read + by the assigner before the rule, the one exception; ADR 0682's review raised it and the record says it. Principle 4. +- **H-A-6 The seat that serves `validate`**: the seat that runs the composition step, which G §22 names `mesh-wants`; + ADR 0682 §4's "mesh-module-assigner" is corrected to that seat (asked of the record writer, 01:38). Principle 9. +- **H-A-7 The main file's size** (258 KB against the 80 KB bound of playbook 02): the reshaping of design 47's main + file into its milestones' parts is a change of its own after H0, not folded into this one (rules-are-weighed: the + bound protects a reader, and the plan's reader has the three H part files; a 180 KB move in the same pull request + would hide the lines under review). Said to the operator at 01:38. +- **H-A-8 The build modules' queue order**: deliveries first (ADR 0525 §4), as §753 writes; the operator's yes to the + turns of 2026-11-15 is in no record, so the record holds. If H2's prepare finds it, the record gets an insight.