Answer A-389: before the catalog half is read, a module's call of another module's tool runs unmarked, logged
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
This commit is contained in:
@@ -857,3 +857,11 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
half is read; principles 3 and 7) A-387's start path takes a verb whose definition names the class `read` explicitly,
|
||||
never one that names none. The broker seat's contract classes `list`, `show`, `check` and `orphans` as `read`, and its
|
||||
bootstrapped copy follows, so A-375's `mesh-broker.list` still passes.
|
||||
- **A-389** (completes A-387 for module tools, met a fifth time: live 02:32 the take-in's
|
||||
`mesh-delivery-forge-bridge.bridge_merged_message` is refused "the marks of mesh-delivery-forge-bridge are not read
|
||||
yet"; a module tool names no class, and its marks live only in the catalog half's entry the take-in has not made yet;
|
||||
principles 7 and 3) Before the catalog half is read, a module tool whose proven caller is another module's account (never
|
||||
a session's or the console's) runs unmarked, and the runner logs each such call once per tool with its caller ("run
|
||||
unmarked before the catalog half is read"); a module tool called otherwise waits and is judged as before. A module
|
||||
tool's mark is read again, and holds, from the call after the half is read. Today the one marked module tool,
|
||||
`gitea_branch_protection_loosen`, has no module among its callers.
|
||||
|
||||
Reference in New Issue
Block a user