From 480a85763550aae7d43d907f8cf14252c59b9628 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 19:31:12 +0100 Subject: [PATCH] Answer A-301: the view's answers tool is the SDK's first-view tool with its callers list Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 3 +++ 1 file changed, 3 insertions(+) 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 d5d87e24..d035d0eb 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 @@ -473,3 +473,6 @@ the principle that settles it, cited as "design 47 G A-n". 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. +- **A-301** (§717, A-131; principle 7, one form per seat view) The status view's first-view tool `answers` is mesh-sdk's + first-view tool (the one with a callers list, as the assigner's `asks` and `wants` are), its callers the teller in + A-131's form; §717's "views.ReadTool" reads as this.