From c096c4af1c8e2ebf99b1e76bf7796daaf0dfed82 Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 23:21:30 +0100 Subject: [PATCH] Answer A-88: no callers named in mesh-networking's seats Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md index f254df8b..6c4c1ab6 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md @@ -342,3 +342,5 @@ names the principle that settles it, and is cited as "design 47 G A-n". - **A-87** (§568, §589, A-70, A-76; principle 7) As built in mesh-delivery bd228d51: a fault with no node says `no node`; `FaultClass` maps `buildstep.PassingCause`'s words onto A-76's four classes. `builder_build`'s `newest: ` is read by the tools bundle following the catalog half itself, as A-70 has it for `reserved`. +- **A-88** (§610, the main file's item 85; principle 7) mesh-networking's A-N1 (callers named in its seven seat + definitions) is not brought in: from G no verb names its callers (§610), which supersedes item 85's reading.