From 9925385b24e443bfa90f545a2365ec0bcfaedd77 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 22:05:49 +0100 Subject: [PATCH] Design 47 H: H-A-197, every pull loop claims through the SDK --- 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 8f8e2ee9..4619ad1c 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 @@ -1050,3 +1050,8 @@ Where two preparers disagreed, the chosen one is named. refuses, loud at bind time, a second pull loop on a durable the same process already pulls (the error names the durable and both binders), so the kind cannot run in silence again; the cause itself is delivered by the tool runner's own release (H-A-132/133). P1 (failure must be loud), P7. +- **H-A-197 (every pull loop claims through the SDK, 22:05)** Met in the build of H-A-196: the tool runner binds its + durables through the bus client directly, so the SDK's guard would not have seen the two loops that caused the + fault. Every module's pull loop, the tool runner's included, claims its durable through the SDK's one guard before it + pulls (P7: shared behaviour lives in the SDK), and a re-serve stops its old loop before it binds the new one so the + guard refuses only a true second loop. P1, P7.