From 4fa58916976e176eb7a0eba79127c193e18365d9 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 19:30:54 +0100 Subject: [PATCH] Correct A-300: the view's tools keep assigner_read_wants, since a first view does not read by key or history Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) 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 91f034db..d5d87e24 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 @@ -469,6 +469,7 @@ 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...view`, `restore....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. +- **A-300** (§717, A-131, A-210; principles 4 and 7) The status view's process follows the wants by its seat-form + first view; its tools program keeps the invoke `assigner_read_wants`, because the view's tools read a want by its + key and its history (`view_tiers`' since of a want, `assigner_want`), which a first-view tool (pages after a + position) does not answer; `assigner_read_asks` and `assigner_read_assignments` go as §717 says.