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 ffea790b..56c31707 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 @@ -2456,3 +2456,29 @@ Where two preparers disagreed, the chosen one is named. digest is refused naming both. The pack is reproducible (the same archive bytes at 0.1.0, 0.1.1 and the refused publish). Recovery: rerun the build steps once the distribution module runs on novox. A-490j, P-failure-loud, fix-a-bug-met-twice (the same symptom met 19 Nov). +- **H-A-388 (the have carries the applied run; the declaration's version is its form, 00:26)** E4b, E7b. (1) The + node-engine's have value gains `run` (the composition run's sequence the module was applied from) in + seats/node-engine/seat.json, generated, its form raised by one as H-A-352 (2) has it; the node-engine's developer + makes that K row in the mesh-contracts worktree (one commit citing this answer) since no other developer holds it + tonight, and tells the lead both heads. (2) The declaration carries no form beside its Version, so Version is its + form (one field per thing, P3): mesh-sdk's declaration gains the process's drain-bound under Version raised by one, + the composer (the assigner, mesh-delivery) writes that Version, the node-engine reads it and refuses a higher one as + it does today. The edge the delivery plan derives: the node-engine's manifest states the declaration Version it reads + (`declaration-reads`, beside its manifest reads of ADR 0614) and the composer's manifest the Version it writes + (`declaration-writes`); the plan orders the writer of a Version after every node's engine reads it. Built: the field + and the two manifest words in mesh-sdk (its developer), the engine's word and reader (mesh-host), the composer's word + and writer and the plan's edge (mesh-delivery, with A1-A6). Until the plan reads the edge, the milestone plan names + the order by hand: node-engine before the assigner. design-it-as-it-should-be, P3, ADR 0614. +- **H-A-389 (a validate step judging a candidate that changes a seat's form, 00:26)** The mesh-catalog developer found + the trunk validator refuses H2's delivery seat definitions (form, max-age: fields its format does not know), so a + pipeline's validate step, asked of the running assigner, cannot judge a candidate that raises a seat's form. Today + validate is an optional step (main.175 shows it so), so the H2 group's pipeline is not failed by it; the gap stands: + a candidate that changes mesh-delivery-sdk or a seat's form is judged by a validator built from the candidate's own + heads (ADR 0573 §2's rule for the check, carried to the validate step: the runner builds the validator tool from the + candidate like any artifact and asks it). Queued for H2b in mesh-delivery; the H2 group's validate verdicts are + read by hand once after its merge. design-it-as-it-should-be, ADR 0573 §2. +- **H-A-390 (§799's shared parts are the delivery SDK's developer's, 00:26)** BM1: the shared parts in + mesh-delivery-sdk's steprun (again-delays parsed into Puller.Delay, the third run's "fetch:"/"publish:" why, + HolderSilentOr's assigner call "with no seat call to learn why") are built by the mesh-delivery developer with its B + lines; the mesh-catalog developer builds the three build modules' settings and their use of the conformance kit + against the relayed head. One owner per file (P3).