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 38b54407..c7338651 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 @@ -1471,3 +1471,10 @@ Where two preparers disagreed, the chosen one is named. pipeline-ended event too (the event it already consumes for its records), and on the node-engine's running event where a tier's judgement waits on a machine (ADR 0682: wants by the newest passed release, at once). P-NATS-native (the event that changes the answer drives the pass), ADR 0282 (five minutes from merge to running). +- **H-A-257 (the followed view of the builds: its first view is the watch's handover; a re-watch replaces the view, 12:00)** + Amends H-A-255 (1): the view is the watch's own handover of current values (no page read), kept in memory; a + build's end is read once from its key's history as the view takes the build in (a start reads one history per + build, once per process; the builder's build record carrying its end so no history is read is H2). A watch asked + again after an error replaces the view whole with the new handover, so keys deleted in the gap leave it. A pass + may still read what it judges beside the builds (the builder's log, the registry's list): one call each per pass. + P7, P4.