From c9abb1c5f92e2216b8a980cf487510d42736bcb7 Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 9 Nov 2026 20:12:00 +0100 Subject: [PATCH] Test 58 names a part not heard, not a node away: a check still passes a sleeping node with a warning MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The test read as failing every check while a node sleeps, against ADR 0593 §9 and the design's own try section. Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ --- .../01-to-be/47-delivery-from-commit-to-delivered.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md b/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md index e170de4c..2c371b94 100644 --- a/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md +++ b/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md @@ -2703,12 +2703,12 @@ What milestone G's prepare found, and its test: 57. **The indexer reads every definition at its start.** Started with a definition on a contracts trunk that no event announced, the indexer judges the first manifest claiming that seat with it, and answers it in `seat-definitions` (whole, indexer). -58. **A check that could not run says so and is asked once more.** A check whose composer's node does not answer - reads `could not run` and names that node in `mesh-delivery.show`; the claim is released; the node's `running` asks - the check again once, and a second `running` of the same part at the same fingerprint asks no second check; a +58. **A check that could not run says so and is asked once more.** A check that a part of the mesh it needs does not + answer (the composer, the forge, a build seat's holder) reads `could not run` and names that part in + `mesh-delivery.show`; the claim is released; the part's `running` asks the check again once, and a second `running` of the same part at the same fingerprint asks no second check; a `could not run` not asked again within 60 minutes raises `check-could-not-run`, which reads cleared once the heads - are checked again, replaced, or their pull request closes (whole, checker; live, read through - `mesh-delivery.show`). + are checked again, replaced, or their pull request closes; a placed node away is not such a part: the check passes it + with a warning (ADR 0593 §9) (whole, checker; live, read through `mesh-delivery.show`). 59. **A session hears an accepted record** (issue 595). An Approve that accepts a record makes the knowledge base say `reviewed` with what was accepted, by the operator and with the warrant, and the tool runner's account hears it, so a session waiting with `mesh_wait` wakes on it (whole, knowledge base; live).