21 lines
794 B
Markdown
21 lines
794 B
Markdown
# 2026-05-15 COACH Bootstrap
|
|
|
|
## Context
|
|
|
|
The user reported that the multi-agent workflow was becoming hard to follow because internal task IDs, sync failures, and cross-window coordination required too much manual intervention.
|
|
|
|
## Decision
|
|
|
|
Add COACH as a guidance role carried by the main user-facing chat. Do not open a separate COACH agent by default.
|
|
|
|
## Outcomes
|
|
|
|
- `USER_STATUS.md` becomes the user-facing state page.
|
|
- ORCHESTRATOR remains responsible for task state and acceptance gates.
|
|
- CORRECTION remains responsible for sync-health and drift monitoring.
|
|
- COACH focuses on usability, next-action clarity, session freeze, and knowledge capture.
|
|
|
|
## Follow-Up
|
|
|
|
Before entering OpenClaw connection/setup work, confirm the target system design and acceptance criteria with the user.
|