mirror of
https://github.com/dtzp555-max/memory-continuity.git
synced 2026-07-21 21:15:07 +00:00
Add hard forwarding protocol for execution-agent updates
This commit is contained in:
@@ -40,7 +40,11 @@
|
||||
- Current important exception / newer rule: **codex_worker** should use **primary** = `openai-codex/gpt-5.4`, prefer high/extra/xhigh thinking when available, and should **not auto-fallback** to another model. If its primary model is unavailable, report to Tao and let Tao decide the replacement model.
|
||||
- Additional long-lived execution agents initialized locally for repeat use: **docs_worker**, **qa_worker**, **ops_worker**.
|
||||
- Execution-agent system needs a standardized dispatch/handoff layer: task input template, result format, blocker/escalation rules, and a **main-to-Tao forwarding rule**.
|
||||
- New hard rule: when an execution agent reports acceptance, milestone progress, blocker, or completion, **main must update Tao first before continuing with review/commit/next-step work**. If worker completion is not forwarded, treat that as a main-process failure rather than “still working”.
|
||||
- **Hard reporting/forwarding protocol (must-follow):**
|
||||
- Worker events that require immediate Tao-visible updates (no “I’ll summarize later”): **accepted**, **milestone result**, **blocked/failed**, **completion**, **agent switch decision**, **transition to review/commit/release**.
|
||||
- **Ordering constraint:** when a worker reports milestone/completion, main’s *first* action is to update Tao; only then proceed to review/commit/next dispatch.
|
||||
- **Failure definition:** if a worker has already reported completion and main has not forwarded it to Tao, that is a **main process failure**, not “task still in progress”.
|
||||
- Default 4-line update template: **who / status / output / next**.
|
||||
|
||||
## 8) Watchdog / automation policy
|
||||
- Tao preference: avoid watchdog-style auto-restart automation.
|
||||
|
||||
@@ -0,0 +1,40 @@
|
||||
# 2026-03-08
|
||||
|
||||
## Main ↔ execution agent 回包强制汇报协议(新增硬规则)
|
||||
Tao 指出问题本质:不是 worker 卡住,而是 main 没把“worker 已回包”当成必须立刻对 Tao 可见的状态变化。
|
||||
|
||||
### 强制汇报事件(state-change triggers)
|
||||
只要出现任一情况,main 必须立刻向 Tao 汇报,不能继续闷头做后续工作:
|
||||
- 执行 Agent 已接单
|
||||
- 执行 Agent 给出里程碑结果
|
||||
- 执行 Agent blocked / failed
|
||||
- 执行 Agent 完成一轮交付
|
||||
- main 决定切换到另一个 Agent
|
||||
- main 决定从执行转入 review / commit / release
|
||||
|
||||
### 转发义务(顺序硬约束)
|
||||
执行 Agent 一旦回 milestone/completion:
|
||||
1) main 的第一动作必须是给 Tao 发状态更新
|
||||
2) 然后才能做 review / commit / 下一步分派
|
||||
顺序不能反。
|
||||
|
||||
### 极简汇报模板(默认 4 行)
|
||||
- 谁:哪个 Agent
|
||||
- 状态:ok / blocked / failed
|
||||
- 产出:改了什么
|
||||
- 下一步:我准备怎么接
|
||||
|
||||
### 失败定义(狠规则)
|
||||
若执行 Agent 已经回包而 main 未向 Tao 转述:
|
||||
- 视为 main 的流程失败
|
||||
- 不是“任务还在进行中”
|
||||
|
||||
### 建议的任务状态枚举(未来状态面板用)
|
||||
- planned
|
||||
- dispatched
|
||||
- in_progress
|
||||
- blocked
|
||||
- reviewing
|
||||
- done
|
||||
|
||||
Next: 把以上规则写入长期记忆(MEMORY.md)并补进 execution-agent-dispatch skill。
|
||||
Reference in New Issue
Block a user