openclaw-control-plane/handoff/ORCHESTRATOR.md

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.
• G0 is complete: the user confirmed mission, role boundaries, non-mutation rule, communication MVP, freeze policy, and acceptance criteria.
• 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/.
• The polling sync is intentionally temporary; design an async notification/coordinator layer when PC/VPS baseline work is stable.
• Before verified G1 baseline completion, execution agents may perform only read-only discovery and evidence capture.

Next Actions

1. Keep AGENT_BOARD.md as the source of truth for the initial task run; do not switch to Gitea Issues yet.
2. Assign T3 to PC_EXECUTOR for read-only PC baseline evidence.
3. Assign T4 to VPS_EXECUTOR for read-only VPS baseline evidence.
4. Assign T5 to PC_VERIFIER and T6 to VPS_VERIFIER after executor evidence exists.
5. Keep T7 available for CORRECTION to handle drift, conflicts, unsafe changes, or missing evidence.
6. Require verifier acceptance of G1 before any PC/VPS configuration mutation.

Open Questions

• Has the VPS pulled the latest control-plane repository at /home/ubuntu/openclaw-control-plane?
• When should the async notification/coordinator design start after baseline evidence is stable?

Last Update

G0 completed with user confirmation. Work split into read-only executor baseline tasks, independent verifier tasks, and a CORRECTION drift-monitoring task. No PC/VPS configuration mutation is authorized.