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
2026-11-13 23:15:17 +01:00
parent 0e9b6e5286
commit c1065d9868
1 changed files with 6 additions and 0 deletions
@@ -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_<module>_<name>`); a name neither names stays refused as today.