Answer A-265: the tool runner answers a bundle's marked seat verb as AnswerSeat does
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
This commit is contained in:
@@ -325,3 +325,7 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
a marked verb are added in mesh-sdk's `seatdef.Resolve`, which the seat generator and every reader of a definition
|
||||
(the seat list, the grants part, the validator, `AnswerSeat`) go through: one place, one definition for all; the
|
||||
seat files stay as written.
|
||||
- **A-265** (A-264, design 46 approval mark §20; principles 4 and 7) A-264 holds for every marked definition. Where a
|
||||
tool bundle holds the seat (the login shell's `execute`), the tool runner, which already holds that bundle's gate,
|
||||
answers the marked verb by caller and serves `approvals` for the seats its bundles hold, as `AnswerSeat` does for a
|
||||
process; no holder changes and no mark moves.
|
||||
|
||||
Reference in New Issue
Block a user