From cb1ce7291f35b164ac6aa143b8e8774cb6db417b Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 17 Nov 2026 09:38:02 +0100 Subject: [PATCH] Answer A-465a: a composition input is kept once per content, shared by the asks that use it --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 7 +++++++ 1 file changed, 7 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 1196619d..7294641e 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 @@ -1515,3 +1515,10 @@ the principle that settles it, cited as "design 47 G A-n". (Live, 2026-11-17 08:56: every composition step of source 992's 25 pipelines could not run, "the state inputs is at its cap of 64 MiB (66318968 bytes kept)", while `assigner_inputs` listed 10 inputs of about 14 MB: the rest were objects of deleted keys.) +- **A-465a** (A-465; principles 7 and 3) The assigner keeps a composition input once per content: its key is the + input's sha256 alone, and each ask names the digest it uses, so every composition step of one revision that asks the + same node's input shares one kept input. An input is deleted, with its object, when no ask that names it is still + running (each `step-ended` removes its ask's name, and the input goes with the last), or a day after its last write. A + composition request the cap still refuses ends its step "could not run", as now, naming the fill. (Live, 2026-11-17 + 09:32: twenty composition steps asked again at once kept a copy each of the same four node inputs, 1.1 to 1.5 MB each, + and the state was at its 64 MiB cap again within ninety seconds.) -- 2.54.0