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
+14
View File
@@ -7,6 +7,20 @@ description: Standardize how main dispatches work to execution agents and how ex
Use this skill after execution architecture is decided.
## Status / scope boundary
This skill is a **workflow / protocol skill**.
It standardizes dispatch packets, worker replies, escalation points, and main-to-Tao forwarding discipline.
It is **not** a runtime transport fix.
It does **not** create stable bidirectional communication between OpenClaw agents, subagents, or ACP sessions.
It does **not** guarantee parent-first completion routing, persistent child↔parent conversation, or reliable agent-to-agent backchannels.
Current project status:
- treat this skill as useful only for **process discipline**
- do **not** treat it as a solution to ACP / subagent communication instability
- if stable agent-to-agent communication is needed, wait for OpenClaw / ACP runtime support to mature first
## Goal
Turn vague delegation into a clear handoff.