From 39b41496877e45c040e07f4b633b6e715dd841b4 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 05:50:28 +0100 Subject: [PATCH] Answer A-192: the watchman hears waits and running, reads no other state Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 6188026b..1d8929c7 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -47,3 +47,7 @@ the principle that settles it, cited as "design 47 G A-n". - **A-191** (§33, §540; principle 3) A `pipeline-failed` finding whose commit no pull request merged, or whose `pull` read fails, is written with no `owner` (so it reaches the operator at once) and says why in its explanation; a failed read is said and the owner is written at the next step end of that commit. +- **A-192** (ADR 0596, ADR 0603 §8, §499, §541, §520; principles 1 and 7) The builder says `wait-held` and `wait-ended` + for a key queued behind a package, in the one wait form with its `part`, and the watchman times it from those; its + reads of the builder's `builds`, the node-engine's `have` and `mesh-host.health` go, replaced by the node-engine's + `running` (with `healthy`) and its wait events.