From cfeee0cf1dc69ab78d3d313f377904d85b60f6c3 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 21 Nov 2026 11:47:49 +0100 Subject: [PATCH] Design 47 H: H-A-250 and H-A-251, the artifact sweep reads once per pass; the tool runner binds a state once --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 14 ++++++++++++++ 1 file changed, 14 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 b2ab4b37..c14e9d8a 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 @@ -1426,3 +1426,17 @@ Where two preparers disagreed, the chosen one is named. once wrote under it; the held writer clears only those keys at start and never the other writer's. The indexer's retired list carries call-unanswered with its own call ids' forms (the ids its seed, tag-floor and versions-fill parts wrote), so the daemon's stale keys clear once and the tool runner's approval findings stay. P7, G ยง580. +- **H-A-250 (the artifact sweep judges from one read per pass, one pass at a time, and stops loud, 11:47)** Met live: + the artifact store's bundle starts a sweep on every finished build and an observation on every want change, each + reading the builder's builds state key by key (ten thousand keys, two bus answers each), the starts queued behind + one lock and draining back to back, and asks the registry's list again at every pass though its answer exceeds the + bus's one megabyte: a third of the night's bus flood. (1) The starts fold into one pending pass: a finished build + or a want change marks the pass wanted; a pass that ends with the mark set runs once more, never once per event. + (2) A pass reads the builds once, as a page of the state (the SDK's paged read) or from a followed view of the + builder's builds, never one get per key. (3) A list the registry cannot answer ends the pass with the finding + artifact-list-unread (scope module) and no retry until the next event; the registry's list answers per repository + or paged (H2, with the one-megabyte kind of row 102). P4, P-NATS-native (an event marks; nothing replays a + state per event). +- **H-A-251 (the tool runner binds a state once, not on every read, 11:47)** Met live: the tool runner's state get + binds the bucket (a stream-info request) before every get, doubling every read on the bus. The runner keeps one + binding per state for the process (re-bound on a bind error), so a read is one answer. In mesh-tools. P7.