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 cc61813d..8b18b18a 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 @@ -1324,3 +1324,13 @@ Where two preparers disagreed, the chosen one is named. (H-A-51), so every rerun of a validate step was refused "placed no ask now", and a composition rerun likewise. The rerun of validate asks the pipeline's one validate ask again; the rerun of composition builds the composition ask for the named mover directly. P4 (a recovery tool that always refuses is a missing tool). +- **H-A-237 (the keeper's warrant asks at approve level until a channel carries destroy; an ask the router holds is said, 11:07)** + Met live: the bus module's drop and rebuild asks are at the destroy level, which needs a code no channel carries + yet, so the router held all four asks unshown and each expired, while the tool answered "the operator is asked". + (1) Until a channel carries a destroy answer (owed, H2: the messenger's carriers and a channel with the code), the + keeper asks its drop and rebuild warrants at the approve level, the ask naming what is removed and that a snapshot + is taken first, with the asker's expiry (the caller's, default sixty minutes); warranted accepts an approve-level + choice for these two acts. (2) The tool reads the router's record of its ask before it answers: offered (where), + held (why: the router's holdWhy names the level), or refused; "the operator is asked" is said only for offered. + (3) The router's holdWhy names the destroy level. A weighed bend, said: the operator is the mesh's one user and + asked for it (2026-11-21 11:13), the snapshot covers the risk; the destroy proof stays designed (ADR 0259).