Answer A-119: the builder's floor from the catalog half, the assignments view in seat form

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 03:28:15 +01:00
parent cb0efaf9a6
commit 17c9525ebd
1 changed files with 5 additions and 0 deletions
@@ -474,3 +474,8 @@ names the principle that settles it, and is cited as "design 47 G A-n".
 - **A-118** (A-77, A-101, §167's checker that goes with G; principle 7) The shared `Asker` takes optional bound keys;
  the builder arms them in its `bounds` state. The checker, which the runner replaces and which goes after G, keeps its
  step bound as today and gains no `bounds` state.
+- **A-119** (§7, §616, A-82, A-116; principles 1 and 7) The builder's floor takes its requirements from the catalog
+  half it already follows (each entry's dependencies), so `indexer_requirements` goes; it is woken by the catalog
+  revisions it already hears, so the forge stream's consume goes; the assignments view is named in the seat form of
+  §616 (`consumes` `seat:mesh-module-assigner.views.assignments`, `reads` `seat:mesh-module-assigner.assignments`, A-116),
+  its first view through the seat's verb `assignments`. No module is named.