From c1065d9868387491ef9b9ed92f608ceebf389f9f Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 13 Nov 2026 23:15:17 +0100 Subject: [PATCH] Answer A-379: the runner reaches a module's old objects by the name its membership gives, beside bindings Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 6 ++++++ 1 file changed, 6 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 1a151b13..e33d7a6f 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 @@ -800,3 +800,9 @@ the principle that settles it, cited as "design 47 G A-n". and A-375. - **A-378** (completes A-376; principle 7) The indexer's first views `modules` and `manifests` name the bus module (`nats`) among their callers, so its keeper reads the catalog holder's manifest. +- **A-379** (replaces A-376 and A-378 for the start: the indexer's `catalog-revisions` is declared in its manifest's + old `objects` section, which grants creates (records.go objectsOf, assertions.go), while the tool runner reaches an + object store only by a new-form binding (node-tools internal/bus/bindings.go objectStore), so nothing binds it; + principle 7: what exists) The tool runner reaches a module's object store by the binding when one is bound, and + otherwise by the old `objects` entry its membership names, under the bus name grants created for it + (`OBJ__`); a name neither names stays refused as today.