novox/hq
9
0
Fork 0
Code Issues Pull Requests 1 Releases Wiki Activity

Answer A-382: every account may list stream names, which hearing an event starts with

Browse Source 
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
This commit is contained in:
jschoubben
2026-11-14 00:06:50 +01:00
parent be264026b5
commit 2c67b2e53b
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md
+5
View File
@@ -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.