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 9d8a676b..c99f5dd5 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 @@ -39,3 +39,55 @@ A question no principle settles goes to the operator or to a record; it is marke 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. + +## From the review by architectural domain (2026-11-20 01:40 to 01:44 CET; four reviewers, one round) + +- **H-A-9 How the apply order reaches the node-engine**: the want carries its `pipeline` and its `rank` in that + pipeline's delivery order, written by the assigner from `pipeline-ended`; the node-engine applies a pipeline's wants + on its machine by rank and consumes no event of the runner. The apply-order read tool is the node-engine's. + Principles 9 and 12. +- **H-A-10 Order across machines** (ADR 0666 §14's "delivered before" edge between machines): no want is held for it + (the operator, 2026-11-17: every machine that places the module installs the latest version); a consumer whose + provider on another machine has not moved yet holds its own entry, says it, and reverts after its bound; the + composition step composed the whole graph before any want was written. ADR 0682 changes §14 so (asked of the record + writer, 01:46). Principles 3 and 7. +- **H-A-11 Publishing an event family stays the producer's**: every account may call every verb (ADR 0682), but a + module publishes only the events its manifest declares, as ADR 0666 §21 has it for a step's result; the mechanism + stays whole, who is on which side is not asked (who-may-is-not-the-operators-question). An enrolling node's account + keeps its own grant. Principle 6. +- **H-A-12 The indexer's consumer and a blocked `source-moved`**: one durable consumer per watched branch; a + `source-moved` the indexer cannot take in (the store full) is held, unacknowledged, until the bus module's `room` + wakes it, never on the ack timer; a hand tool skips it with `why`, written in the hand-act log. `take-in.pending`, + `take-in-waits` and `indexer_pending` stay (ADR 0633 §5). Principles 1, 3 and 4. +- **H-A-13 A source revision written once per call**: the gate keys its write by the call id with compare-and-set, so a + redelivered `merge-called` numbers nothing twice. Principle 3. +- **H-A-14 The waiting queue of the runner**: ordered by the runner's own counter at the moment it writes the pipeline; + placed at the runner's start from its own state and on every end, a cancel and a set-aside included; a finding when + pipelines wait while none runs; a pipeline waiting on the operator's `approval` step does not count against + `pipelines-at-once` and re-enters the queue first when approved; the queue's cap is a setting. Principles 3 and 11. +- **H-A-15 The clean state's seams** (plan section 5): before the runner starts, every watched branch's current head is + its first source revision with no movers (§745) and the newest catalog revision names it, read and counted; the state + of the earlier model is dropped after the new programs run (after step 5.6), each item through the tool named for it, + the backup snapshot being the rollback; every new durable consumer starts at the newest message and refuses an event + of the old form with a journal line; the stopped runner's queue of old `take-in.taken` goes with the state; a machine + away at the clean state gets its hand placement when it is back, before anything else; the forge's branch protections + drop the required statuses `mesh/merge-gate` and `mesh/repo-check` in H1. Principles 2 and 3. +- **H-A-16 Where H1's integration tests run before its merge**: once, locally against an embedded bus, said in each + pull request (how-work-is-done allows it); the chain's live proof (plan step 7) is H1's check; from H1 on the + pipeline makes the check. Rules-are-weighed, said. +- **H-A-17 The whole tests**: one per module, in that module's repository; tests 110, 112 and 113 are split per module + and the chain stays the live proof; the design gives the count per module per release and names the retired tests + that free room (the budget is per module, 50 and 500). +- **H-A-18 The forge module's call**: a call key written before the first merge and said again at start; `refused` in + the event's body; `merge-partial` keyed by the call, cleared when a later call lands the refused members or by a + hand clear; tools `forge_calls` and a say-again; `by` recorded beside the caller's bus account; `failed-steps` is + written from the runner's `step-ended` (mover, commit, fingerprint). Principles 3 and 4. +- **H-A-19 Small forms**: no pin for a take-in with no mover; a call with two members on one branch names the last + member's commit in call order; `package-published` carries the source revision that published and its pipeline pins + it and belongs to that merge call's delivery record; `pipeline-ended` carries per mover the released version and + fingerprint and the delivery order, on the subject `...pipeline-ended..`; `pipeline-failed` + is one finding per failing mover, cleared by that module's later passed pipeline; every fixed value (30 days, 64 MiB, + 60 minutes, 10 minutes) is a setting with that default; §765 drops every state §764 retires. Principles 7 and 11. +- **H-A-20 The main file's size**, a must for three reviewers: the lead's bending of the bound (H-A-7) is said to the + operator at 01:48 with the question whether the reshape follows H0 as its own change; until the answer the bound + stands bent, said.