51 lines
2.9 KiB
Markdown
51 lines
2.9 KiB
Markdown
# ORCHESTRATOR Handoff
|
|
|
|
## Role
|
|
|
|
Own requirements alignment, task decomposition, dependency tracking, and final acceptance.
|
|
|
|
## Current Objective
|
|
|
|
Bootstrap the shared Gitea-backed control plane, then coordinate read-only baseline discovery on PC and VPS.
|
|
|
|
## Must Read
|
|
|
|
- `AGENT_BOARD.md`
|
|
- `OPENCLAW_EXEC_NODE_PLAN.md` from the PC workspace if available
|
|
- All role handoff files relevant to active tasks
|
|
|
|
## Current State
|
|
|
|
- Standalone Gitea repository: `https://git.smartmotor.cloud/wangzhendong/openclaw-control-plane.git`.
|
|
- PC local path: `D:\openclaw-control-plane`.
|
|
- VPS target path: `/home/ubuntu/openclaw-control-plane`.
|
|
- Access mode: HTTPS.
|
|
- Default branch: `main`.
|
|
- G0A collaboration mechanism is complete: the user confirmed agent roles, Git polling MVP, sync-health handling, `USER_STATUS.md` as user entry, and non-mutation/freeze boundaries.
|
|
- G0B OpenClaw system requirements are pending: final system effect, component responsibilities, PC execution permissions, Tailscale role, phone Control UI path, later channels, and G2/G3/G4 acceptance criteria must be discussed and frozen with the user.
|
|
- G1 baseline is complete: PC_VERIFIER accepted T5 and VPS_VERIFIER accepted T6.
|
|
- Strict `smartmotor.cloud` website freeze is a hard requirement during filing review.
|
|
- Communication MVP uses polling Git sync scripts in `sync/` and task files in `tasks/`.
|
|
- Sync-health recovered; T7 is no longer blocked and remains claimed for ongoing CORRECTION monitoring.
|
|
- Mutation-stage work and G2 are not authorized while G0B is pending.
|
|
- `USER_STATUS.md` is the user-facing status entry; internal agent ledgers should not be required reading for the user.
|
|
- The polling sync is intentionally temporary; design an async notification/coordinator layer when PC/VPS baseline work is stable.
|
|
|
|
## Next Actions
|
|
|
|
1. Complete G0B with the user before opening G2.
|
|
2. Keep T7 active for CORRECTION monitoring of sync-health, drift, missing evidence, and freeze-policy risk.
|
|
3. Keep `USER_STATUS.md` current when gate, blocker, heartbeat, or required user decision changes.
|
|
4. Track the VPS verifier follow-up observations before any future mutation task: service path naming drift and Nginx route/config anomaly.
|
|
5. Do not open G2 or any mutation-stage task until G0B is accepted and the user explicitly authorizes the next stage.
|
|
|
|
## Open Questions
|
|
|
|
- Has the VPS pulled the latest control-plane repository at `/home/ubuntu/openclaw-control-plane`?
|
|
- Should Gitea Issues be used immediately for task tracking, or should `AGENT_BOARD.md` remain the first source of truth for the initial run?
|
|
- When should we upgrade from polling sync to webhook or Cursor SDK based asynchronous coordination?
|
|
|
|
## Last Update
|
|
|
|
Corrected gate model: G0A is complete, G0B is pending, and G1 baseline remains complete. G2 and mutation-stage work remain unauthorized until OpenClaw system requirements and acceptance criteria are confirmed with the user.
|