From 3631a151a31a2ba6afe54752dd32c06fe6ff5945 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 11:19:18 +0100 Subject: [PATCH] Answer A-276: a pipeline-waits finding names its awaited fingerprint in its evidence Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 3 +++ 1 file changed, 3 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 d593d9a3..c8c6b2b2 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 @@ -362,3 +362,6 @@ the principle that settles it, cited as "design 47 G A-n". - **A-275** (ยง558, A-102; principles 3 and 7) The node-engine's self-composition reads a manifest's `invokes` with mesh-sdk's `catalogue.readInvokes`, which reads the short and the long form alike; no part keeps its own reader of a manifest field, and a form it cannot read is refused, never taken as no seats. +- **A-276** (A-218, A-206; principles 3 and 7) A `pipeline-waits` finding names the awaited runner fingerprint in + one evidence entry `awaited `, written when the finding is raised; the runner clears exactly the findings whose + entry names the fingerprint its node-engine says `running` healthy. Its summary is never parsed.