From 7e9ed3abf3022d332e1bc76fac0083fed18830ca Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 22:39:33 +0100 Subject: [PATCH] Answer A-49: the session bound, its end at the channel's close, and mesh/capabilities Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 4 ++++ 1 file changed, 4 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 50be45d5..889bf7f4 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 @@ -193,3 +193,7 @@ names the principle that settles it, and is cited as "design 47 G A-n". read as the others are; `assigner_release` with `how` releases an outside wait and without it ends a put as today; a want held for M's own network says `RuleNotHeld` with words naming the open `machine..network`. As the developer proposed on mesh-delivery feat/47-G-outside5. +- **A-49** (§518, §576; principle 7) A put or get session's bound is the call's bound the runner already uses, + `launch.CallTimeout` (30 seconds), counted from its first chunk; a session also ends when its bundle's channel closes + (the child's exit), as §518 says. The runner answers `mesh/capabilities` with `{words}` (§576), so a bundle's + capability check passes.