Answer A-300: the view's tools read the wants through the holder's first-view tool

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 20:00:56 +01:00
parent 5c98c86d70
commit f522c2114d
1 changed files with 3 additions and 0 deletions
@@ -469,3 +469,6 @@ the principle that settles it, cited as "design 47 G A-n".
  form per kind of mesh-wants' `asks` forms with `.view` after it (`hold.<module>.<fingerprint>.view`,
  `restore.<node>.<module>.<fingerprint>.view`, and so for each), so its generated reader reads every real key; the
  kinds are the seven the asks package writes (hold, restore, backup, record, outside, revert, assignments), not eight.
+- **A-300** (§717, A-131, A-210; principle 7) The status view's tools read the wants through the first-view tool
+  `wants` of the holder A-210 finds (the one they ask for differences), naming mesh-delivery-view among its callers;
+  the invoke `assigner_read_wants` goes with the other two, and no tools program keeps a module-named invoke of its own.