From 491e606472209b0b26dc569bec6c5adf7bcd2fb9 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 09:24:01 +0100 Subject: [PATCH] Answer A-253: a chunked answer reaches a bundle as file Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index b5de6b0e..4ccce29c 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -285,3 +285,5 @@ the principle that settles it, cited as "design 47 G A-n". its `definitions`), depth compose, the one machine, one case `change`. A machine's node-engine build is what the assigner keeps from the node-engine seat's own events, never read from the node-engine's bucket; where the step's revision's node-engine entry differs from the trunk's, that build serves every machine. One run ask per machine. +- **A-253** (A-249; principle 8) The tool runner hands a bundle a chunked answer as the verb's own answer with the + whole file added as the member `file` (base64).