From 2c67b2e53bd6a5684da71f645069c32ed605abf9 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 00:06:50 +0100 Subject: [PATCH] Answer A-382: every account may list stream names, which hearing an event starts with Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 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 6bef9ed9..6aa32edc 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 @@ -815,3 +815,8 @@ the principle that settles it, cited as "design 47 G A-n". reaches the create and SEAT_mesh-conditions_findings-asked stays missing; every bundle with a finding writer exits; principle 7) Grants' own account carries `$JS.API.STREAM.NAMES` (the read its assertion of kept streams starts with), composed with the create rights of A-364. +- **A-382** (widens A-381 to its kind, met a second time: live 00:02, every G bundle with a finding writer exits "no stream + on the bus carries mesh-conditions.findings-asked", because the tool runner's SubscribeNew finds a stream by subject + through `$JS.API.STREAM.NAMES`, which novox.node-tools may not publish, while EVENTS carries `mesh.seat.*.event.>`; + principles 7 and 6) Every account grants composes carries `$JS.API.STREAM.NAMES`, the read of stream names by subject + that hearing an event starts with; it lists names only.