From cb1b71763836c47050161c083d01ee15ed5cb2e8 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 22 Nov 2026 14:09:11 +0100 Subject: [PATCH] Design 47 H2: H-A-471 second addendum, plain merges need a read view --- 03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md | 4 ++++ 1 file changed, 4 insertions(+) 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 a2214380..ffcfc742 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 @@ -911,3 +911,7 @@ The lead's one-line answers to the questions H2's develop and review raise (impl today, since no field the runner and the composer share says which modules the runner reads for; the stray ones are named by durable-orphaned and removed with the tool. A field that says who reads a module's events (its own program, the tool runner, or both) is the thorough shape, noted for H2b. P3, rules-are-weighed (said). +- **H-A-471 (second addendum, 14:40)** A member is merged plainly only from a watched-branches view the forge module + has read since the last registration-changed it heard; while the view is unread or stale, every member is refused as + before ("the watched branches are not read yet"), never merged with the note. The holder keeps the time of its last + read and of the last change heard; a read that fails is retried and said. P-failure-loud.