Clarify execution-agent-dispatch scope and harden gateway rules

This commit is contained in:
2026-03-12 19:33:24 +10:00
parent 6ba8353506
commit 22e6292aba
5 changed files with 31 additions and 1 deletions
@@ -0,0 +1,6 @@
# 2026-03-12 execution-agent-dispatch status
- Tao confirmed the remembered conclusion: `execution-agent-dispatch` was tested before and did not solve the real inter-agent communication problem.
- Durable conclusion: the skill only helps with dispatch structure, worker reply format, escalation rules, and main-to-Tao forwarding discipline.
- It does **not** provide stable bidirectional communication between OpenClaw agents/subagents/ACP sessions.
- Current policy: freeze further development of this skill as a communication-layer solution; wait until OpenClaw ACP/runtime support is stable before resuming work in that direction.