From cf0ac158a73c70dfbbee9cd1803ce025edb0707d Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 19:00:55 +0100 Subject: [PATCH] Design 47 H: H-A-178, the restore point before the placements are read; the finding's id --- 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 d22c2983..52e05bca 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 @@ -934,3 +934,8 @@ Where two preparers disagreed, the chosen one is named. raises the finding `restore-point-missing` (warning, scope the machine, id the module) that clears at the next take-in with a point; it holds only where a holder is placed and does not answer (that is the holder's fault, said as today). P3 (loud, never a silent skip and never a silent hold), P7, H ยง456. +- **H-A-178 (the restore point before the placements are read; the finding's id, 19:00)** Met in the review of + H-A-177: before the node-engine's watch of the assignments has caught up, the placements cannot show that no holder + is placed, so the point is asked as before and a missing answer holds the move (never a move on a guess, P3); and + the finding `restore-point-missing` is keyed by scope, id and kind across the mesh, so its id is `.`, + as the engine's held findings are keyed, never the module alone. P3, P7.