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 eabf8744..5de585f4 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 @@ -730,3 +730,10 @@ The lead's one-line answers to the questions H2's develop and review raise (impl the acts embedded in it (they are notes and views of a few records in flight at the delivery, whose loss changes nothing the operator relies on; said in the commit), and writes acts only as entries of their own from then on. No transition form, no replay of old acts. design-it-as-it-should-be, rules-are-weighed (said). +- **H-A-458 (the node-engine's review round 1: the applied run's branch; drift in the composition answer; the taken + bound, 03:55)** (1) H-A-429 (1): the have keeps the applied run with its branch (the want's `pipeline`), the node-engine + seat's have form raised once and regenerated (mesh-contracts), and settleOne compares a want's run against the have's + only when the branches are equal; a want of another branch replaces whatever stands (P3: one record of what runs, + with the two facts a comparison needs). (2) H-A-392 (b): the composition answer gains `drift` (id, path, drift), the + seat's form rises to 4, regenerated, as H-A-388 (1) did for run. (3) The taken state's write is bound by the ask's own + deadline (the compose call's context passed through Env.Taken), no bound of its own (P11). P3, P11.