From 33d25c50742e75583a20d00ddc7eeeb0f5102d2c Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 3 Nov 2026 13:29:36 +0100 Subject: [PATCH] mesh-watcher: the glossary's words, the delivery gate and the status view --- .claude/agents/mesh-watcher.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.claude/agents/mesh-watcher.md b/.claude/agents/mesh-watcher.md index b7994531..9062e6e9 100644 --- a/.claude/agents/mesh-watcher.md +++ b/.claude/agents/mesh-watcher.md @@ -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. **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 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.