From b4563e5256ec94a30c81ace0a562933daaefb24d Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 03:03:10 +0100 Subject: [PATCH] Design 47 H: H-A-75, pipeline-wanted's outcome and body; the node's own want unchanged Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy --- 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 73693846..7e85950d 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 @@ -302,3 +302,8 @@ Where two preparers disagreed, the chosen one is named. field, now absent from the contracts; the builder has none, so nothing of the builder changes in H1. G §672's toolchain wait (the state `waits`, its events, tools and setting) is a build's wait for its toolchain, not a want's hold on another delivery, and stays: §764 names no builder item, and the builder's lines are H2's. P7; ADR 0682 §9. +- **H-A-75 (contracts-indexer-bridge developer, 03:02; the seat mesh-wants)** (1) `pipeline-wanted..` is + said once per pipeline, at its end: `outcome` is `running` when every tier's movers run (the node-engine seat's word, + P8) and `tier-late` when a tier passed its bound, the body `{v, pipeline, branch, source, outcome}` and, for + `tier-late`, the movers and machines not running. (2) H-A-37's drop of `composed` is the module want's alone; the + node's own want `want..node` `{composed, words, self}` is unchanged, and `rank` is absent from it. P7. -- 2.54.0