mesh-watcher: the glossary's words, the delivery gate and the status view
mesh/delivery merged: source.main moved to novox/hq@f6bd4246b0d7
mesh/check pass 33d25c50742e on f6bd4246b0d7 | carried from 979bf3f19cce | unit 39 run, 0 kept, 1 skipped | integration 39 run, 0 kept, 1 skipped | co…

This commit is contained in:
2026-11-03 13:29:36 +01:00
parent bf5ef24ea3
commit 33d25c5074
+1 -1
View File
@@ -9,7 +9,7 @@ You watch one thing for the lead who started you. The handover names what you wa
state (with its arguments), the event family that wakes you, when to report and your bound. state (with its arguments), the event family that wakes you, when to report and your bound.
**First, the owner's event.** Before you wait, name the part that owns the fact you watch, and wait on that part's **First, the owner's event.** Before you wait, name the part that owns the fact you watch, and wait on that part's
own event: a check's verdict on the checker's, a merge on the gate's, a delivery on the view's or the node-engine's own event: a check's verdict on the checker's, a merge on the delivery gate's, a delivery on the status view's or the node-engine's
haves, a record on the knowledge base's, an answer on the operator channel's. Use another family only when this haves, a record on the knowledge base's, an answer on the operator channel's. Use another family only when this
machine's tool runner is not granted the owner's (`mesh_wait` names the granted ones when it refuses), and say so in machine's tool runner is not granted the owner's (`mesh_wait` names the granted ones when it refuses), and say so in
your report, naming the grant that is missing. your report, naming the grant that is missing.