From 64ff3fd4e9477be0caf4cf5da39984797ee68929 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 17 Nov 2026 09:00:02 +0100 Subject: [PATCH] Answer A-465: the assigner's composition inputs end with their objects, and a drop tool for those left --- .../01-to-be/47-milestones/G-22-lead-answers-2.md | 10 ++++++++++ 1 file changed, 10 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 430a73f7..1196619d 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 @@ -1505,3 +1505,13 @@ the principle that settles it, cited as "design 47 G A-n". 08:51:31: the start comparison asked the seat `git` two seconds before the tool runner on its node served it, every read answered "no responders", it moved nothing and nothing compared again; the heads were moved by hand with `gate_source_follow`.) +- **A-465** (ADR 0595 §4, ADR 0666 §16; principles 3, 4 and 7) The assigner's composition inputs end whole: when the + assigner deletes an input's key itself (the build seat's `step-ended` of its ask, or the sweep of a day-old key), it + removes the object that key names with it, as the indexer removes the objects of its own ended inputs; at its start + it removes every object of the state `inputs` whose key is gone, said in its log with their count and bytes. The tool + `assigner_inputs_drop` (why; a hand act) removes the objects whose key is gone now and answers what it removed, and + `assigner_inputs` lists them as key-gone with their sizes. ADR 0666 §16's "until the drop tool removes it on a + person's word" holds for an object whose key another part deleted; an owner that ends its own key ends its object. + (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.)