Answer A-384: a runner may make the ordered consumers its bundles hear new events on
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
This commit is contained in:
@@ -825,3 +825,9 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
the list in force while the catalog half is unread; principles 7 and 3) A right every account carries (A-382) is added
|
||||
to every account grants writes, a kept one included: keeping an account in force never withholds what every account
|
||||
is given. A pass that only adds still never takes from a loaded user.
|
||||
- **A-384** (completes A-382/A-383 for the whole hearing path, met a third time: live 00:35 "an ordered consumer of
|
||||
mesh-conditions.findings-asked on EVENTS: context deadline exceeded", the runner account holds only INFO of named durables
|
||||
on EVENTS; principles 6 and 7) Every tool runner account carries what the runner's SubscribeNew (an ordered consumer from
|
||||
the next message, mesh-tools node-tools internal/bus/subscribenew.go) asks of the stream that carries the events its
|
||||
bundles hear: the create of an unnamed consumer filtered to those events' subjects, its next-message fetch, its info and
|
||||
its delete, on EVENTS and on every kept seat stream; the same form for every runner, composed in one place.
|
||||
|
||||
Reference in New Issue
Block a user