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 87c149a1..93fbcd0b 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 @@ -717,3 +717,11 @@ The lead's one-line answers to the questions H2's develop and review raise (impl invokes, its state, asks), so it runs on an account of its own granted exactly that, as the runner's process does; the validator's rule stands unchanged. A grant the process lacks at run time is a loud fault of the declaration, caught by the module's whole test. ADR 0436 ยง6, P-failure-loud. +- **H-A-454 (third addendum, 03:40)** Two corrections to the second: the runner's process declares no `bus` (the builder's + is the first process of mesh-delivery with one), and no whole test runs a process under its composed grants tonight, + since the composition of a process account's permissions lives in the grants module alone and no design line gives the + SDK a composer. The builder's whole test runs on the embedded bus as the module's tests do; the declaration's proof is the + validator (every emit, consume, invoke, state and queue the process does is named) and the live case at the builder's + first start after the delivery, which the lead watches: a missing grant refuses the first act loudly in the builder's + journal and is a fix of the declaration. A permission composer in the SDK, so a whole test can run under a process's + grants, is noted for H2b. P-failure-loud, rules-are-weighed (said).