From ad5284889b2339763e64047ebd175e7cf49e5ebc Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 22 Nov 2026 00:10:25 +0100 Subject: [PATCH] Design 47 H: H-A-386, the keep's prefix is _keep/; the runtime's put answer carries the fill --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 6 ++++++ 1 file changed, 6 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 a3b4867d..8bedd2c6 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 @@ -2437,3 +2437,9 @@ Where two preparers disagreed, the chosen one is named. there; the 64 KiB cap holds per entry. (3) The catalog half, when it moves, is a mover with an entry of its own (`..mesh-catalog`, no node) and counts in the head's movers. (4) The month list (type held) stays the way the ledger is listed; nothing changes it. One way per thing, P3; ADR 0595 ยง3. +- **H-A-386 (the keep's prefix is `_keep/`; the runtime's put answer carries the fill, 00:14)** Corrects H-A-380 (2): + the bus refuses a key-value key beginning with '.', so the keep lives under the reserved prefix `_keep/`, the + underscore form the tool runner already uses for `_meta` (H-A-351); everything else of H-A-380 stands. DMC-14, which + H-A-350 answered and no build map carries: the tool runner's put answer (mesh/state.put) carries the entry's fill as + `{"revision": n, "fill": {"count", "bytes", "max_bytes"}}`, buscalls.Fill's form, which mesh-sdk's bundle-side prune + helper reads; built by the mesh-tools developer in H2 beside T1, tested in the runtime's state tests. P3, H-A-227.