Design 47 H: H-A-133, the follower on a module's own runtime hears when its bundle subscribes
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
This commit is contained in:
@@ -595,3 +595,10 @@ Where two preparers disagreed, the chosen one is named.
|
||||
process; no second durable (a consumer the grants part would have to make, H-A-30; P7, P12 a module writes only its
|
||||
own). Fixed under H1 (playbook 08, mesh-tools) before the clean state goes on. A durable bound twice in one process is
|
||||
a kind: the reviewer reads every other bind in the runtime for it.
|
||||
- **H-A-133 (the follower on a module's own runtime hears when its bundle subscribes, 11:33)** With H-A-132 the branch
|
||||
follower of a module's own runtime is handed the events the module's consumer delivers to its bundle. It therefore
|
||||
hears from when the bundle subscribes, waits while the bundle reloads, and loses an event the bundle fails five
|
||||
times (the durable's limit), said in the journal. That is accepted: the follower exists to serve that bundle's
|
||||
first views, so a bundle that never subscribes needs no follower (P7), and acknowledging before the bundle took the
|
||||
event would lose the bundle's (P3). A lost event's picture catches up on the next one of its family; a re-ask on
|
||||
that loss is a finding for H4. The machine's runtime keeps its own binding.
|
||||
|
||||
Reference in New Issue
Block a user