From 93c7714c0d0e93e70f5f8961a69fa09bc9eb8be2 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 21:17:57 +0100 Subject: [PATCH] Design 47 H: H-A-189, a mover's unlogged entries live under its mover key; list answers records --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 5 +++++ 1 file changed, 5 insertions(+) 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 cbaf9012..0b77761e 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 @@ -1005,3 +1005,8 @@ Where two preparers disagreed, the chosen one is named. (H-A-184). The module's version decides (P7: what the builder and the reservation already do): a package artifact's `series` names the module's version series or is left out, the catalog's check refuses a mismatch, and an importer of a package from a module at another series names that series in its manifest's `packages`. P7, P3. +- **H-A-189 (a mover's unlogged step-log entries live under its mover key; list answers records, 21:17)** Met in + the review of H-A-187: the record still kept every ended step's unlogged step-log entry, so a step log outage across + a large pipeline grows the record the same way. A mover's unlogged entries live under its own mover key beside its + steps, written in the same compare-and-set, and the tools' append reads them there; `list` answers each pipeline's + record with a count of its movers and steps, never the steps (one asks `show`, with a mover, for those). P1, P4, P7.