From dfe0963bbf0f5d6d21f5ff178cad6808ece45bdd Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 21 Nov 2026 01:54:46 +0100 Subject: [PATCH] Design 47 H: H-A-227, a fill is read from the store's own figures, never by listing it --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index ed540d92..ef54e99e 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -1253,3 +1253,12 @@ Where two preparers disagreed, the chosen one is named. a take-over dropped stays a gap, which harms nothing (pins read what the registry published; a series' newest is untouched). The series key's list of withdrawn numbers keeps only those above the catalog's highest released patch; the others are refused by the plain rule and dropped at the next write. P3, P1. +- **H-A-227 (a fill is read from the store's own figures, never by listing it; a receiver reads it once, 01:54)** Met + live: the artifact registry's receiver read its incoming object store's fill on every chunk it took, and the tool + runner answered that fill by listing every description in the store, deleted chunks' leftovers included (about + twenty thousand), so one connection read fourteen megabytes a second and the bus ran at full CPU. The tool runner + answers a store's fill from the stream's own figures (bytes and messages the bus keeps), never by listing; the + object count it gives is the stream's live subjects, or none. A receiver reads the fill when a transfer opens and + keeps a running sum per chunk, never a read per chunk. A store whose live objects are far fewer than its kept + descriptions is compacted by its owner (the registry drops the leftovers of deleted chunks when it drops them). + P4 (nothing polls or replays what it does not need), P1.