Answer A-79: the grants part's catalog half, as built, and its last indexer reads go

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 23:06:17 +01:00
parent e67326b6c7
commit 6cf7372ad4
1 changed files with 5 additions and 0 deletions
@@ -302,3 +302,8 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  assigner's `placement` (A-62), and each node's last `running` from the node-engine's stream read whole at start
  (§556); (d) an `inputs` entry is also keyed by its run ask's id, so the build seat's `step-ended` of that ask finds
  and deletes it.
+- **A-79** (§558, §614, §684, §196, §444; principle 7) As built in mesh-delivery 6d483af2: the gate's `source` is named
+  in the short `invokes` form (the manifest's `invokes` is a list of names); the catalog half's rows go into the part's
+  existing `grants_first_views`; while the catalog half is unread the part keeps what the bus loaded and only adds,
+  which is §684's way past the cycle, so no registered branch holds nothing. The part's remaining reads of the
+  indexer's `manifests`, `modules` and `verdicts` go too (§196): the catalog half answers them.