Design 47 H: H-A-132, the tool runner binds a module's consumer once
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
This commit is contained in:
@@ -587,3 +587,11 @@ Where two preparers disagreed, the chosen one is named.
|
||||
module; the forge's own tools refuse a merge by design (ADR 0266). Until hq has a registration of its own (a module
|
||||
whose unit step is its checks, P5: everything ships the same way; built after the clean state), hq's lead answers
|
||||
stay on their branches, pushed, and are cited by branch. Decided as a design detail; told to the operator.
|
||||
- **H-A-132 (one pull loop per module consumer in the tool runner, 11:24)** Met live: in a module's own runtime the
|
||||
tool runner binds the module's durable twice, once for its branch follower (the first views) and once for the
|
||||
bundles' events, so each event reaches one of the two; the catalog-revision of main.1 reached the follower and never
|
||||
the bundle, whose trunk view stayed at revision 0 and whose `revision` verb answered none-yet to every reader. The
|
||||
tool runner binds a module's consumer once and hands each event to both the branch follower and the bundles in
|
||||
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.
|
||||
|
||||
Reference in New Issue
Block a user