From 781b61410025d2f5700aa4bd917e47e890784b99 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 21 Nov 2026 23:56:11 +0100 Subject: [PATCH] Design 47 H: H-A-377, drain-bound is a duration text like every time setting --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 9 +++++++++ 1 file changed, 9 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 3d9d74f8..1ea40645 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 @@ -2353,3 +2353,12 @@ Where two preparers disagreed, the chosen one is named. failed step) and never every step of every mover; stands, kept and why-carried get the description their seat contract names. Built by H2's mesh-delivery developer after its Left list. tools-are-how-a-module-is-spoken-to, one-question-one-tool, P3. +- **H-A-377 (drain-bound is a duration, like every time setting, 23:57)** H-A-358 made the setting drain-bound a whole + number of seconds in the node-engine, and H-A-370 says the node-engine composes a duration setting as its text ("10m") + for the one typed reader: the two meet on the tool runner, where stdio.SettingDuration refuses "30". H-A-370 holds: + a setting that is a time is a duration text everywhere ("30s"), declared, composed and read so; the node-engine + parses it as a Go duration and derives whole seconds only where it renders one for systemd (TimeoutStopSec takes + "30s" as well, so no derivation is needed there either), and its refusal of a non-integer ends. H-A-358's "whole + seconds" is the rendering, never the setting's form. The runner reads drain-bound with stdio.SettingDuration, 30 s + default; no seconds reader is added to mesh-sdk. The node-engine's developer changes drainBoundOf (E3's + counterpart), the tool runner's developer reads it. P9 (one reader, one form), H-A-370.