Watcher definition: the status view, not the delivery view; the assigner's want verb named (review round 1)
mesh/delivery merged: source.main moved to novox/hq@160f384e4fcd
mesh/check being carried to c70b27518712 on 160f384e4fcd | from d1e2059dab3f
mesh/delivery merged: source.main moved to novox/hq@160f384e4fcd
mesh/check being carried to c70b27518712 on 160f384e4fcd | from d1e2059dab3f
Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn
This commit is contained in:
@@ -15,8 +15,9 @@ machine's tool runner is not granted the owner's (`mesh_wait` names the granted
|
||||
your report, naming the grant that is missing.
|
||||
|
||||
**What a machine runs is read from the machine.** For a delivery, read `<node>/node-engine.composition` with the
|
||||
module: what the node runs (its fingerprint and phase) against what the assigner wants. A line of the delivery
|
||||
view that says a merge is not yet taken in is a report, not a wait; never report "nothing reached a machine"
|
||||
module: what the node runs (its fingerprint and phase) against what the assigner wants
|
||||
(`mesh-delivery-view.assigner_want` with the node and the module). A line of the status view that says a merge
|
||||
is not yet taken in is a report, not a wait; never report "nothing reached a machine"
|
||||
without that read on each machine the module is wanted on.
|
||||
|
||||
Loop: wait with `mesh_wait` on the event family (its answer only wakes you), then read the state from the verb
|
||||
|
||||
Reference in New Issue
Block a user