# ORCHESTRATOR Handoff ## Role Own requirements alignment, task decomposition, dependency tracking, and final acceptance. ## Current Objective Coordinate authorized G2 execution strictly under `docs/G2_RUNBOOK.md`: foreground PC node run first, then corresponding VPS pairing approval only after a matching non-secret request/node ID exists. ## 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 complete: QQ and phone Control UI are current-stage control entries, VPS Gateway is the always-on hub, DeepSeek may trigger white-listed actions, Windows PC is the main execution node, Tailscale is optional, and G2/G3/G4 acceptance criteria are frozen. - G1 baseline is complete: PC and VPS baseline evidence were accepted by independent verifiers. - 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/`. - `USER_STATUS.md` is the user-facing status entry; internal agent ledgers should not be required reading for the user. - G2 is authorized as of 2026-05-19, limited to foreground PC node run and corresponding VPS pairing approval under `docs/G2_RUNBOOK.md`. - `docs/G2_RUNBOOK.md` has been prepared as the G2 execution-before-action runbook. It does not authorize execution by itself. - Sync-health is currently healthy: tracked PC and VPS heartbeats are present and clean, and no `sync-state/error-*.md` files are observed in the latest control-plane snapshot. - T2.1 and T8 are now treated as complete control-plane setup work; G2 remains Pending. - The polling sync is intentionally temporary; design an async notification/coordinator layer when PC/VPS baseline work is stable. - Filing-review freeze path wording has been corrected from the obsolete single `docker-composite.yml` reference to `/opt/services/docker-compose.openclaw.yml` plus any equivalent compose/service entries that could affect public website output. ## Next Actions 1. Let PC_EXECUTOR claim T9, write `rollback/pc-g2-node-run-YYYYMMDD.md`, set the Gateway token only in the local shell/session without recording it, and run only the foreground PC node command from `docs/G2_RUNBOOK.md`. 2. Keep `USER_STATUS.md` current when gate, blocker, heartbeat, or required user decision changes. 3. Keep T7/CORRECTION monitoring active for sync-health, drift, missing evidence, and freeze-policy risk. 4. Keep T10 draft until T9 evidence includes a matching non-secret pairing request ID or pending node ID. 5. When T10 becomes eligible, require `rollback/vps-g2-approve-YYYYMMDD.md` before approval and approve only the matching request/node. 6. Continue forbidding service persistence, `openclaw node install/start`, Nginx/Docker/website changes, firewall/network changes, and recording any token or secret. ## Open Questions - When should the user authorize G2 Gateway/node pairing? - When should the Git polling MVP be upgraded to webhook, Issues, OpenClaw events, or Cursor SDK based coordination? ## Last Update 2026-05-19 12:16 UTC+8: User authorized G2 with strict scope. - Allowed scope: foreground PC node run and corresponding VPS pairing approval under `docs/G2_RUNBOOK.md`. - T9 and T13 are ready; T10 remains draft until T9 provides a matching non-secret request/node ID. - G2 quality gate is In Progress, not accepted. - No PC/VPS command was executed by ORCHESTRATOR, no token was handled, no node was started here, no VPS approval was performed here, and no service was modified. 2026-05-19 12:11 UTC+8: Completed G2 authorization-before-execution control-plane cleanup. - `docs/G2_RUNBOOK.md` is complete as the G2 pre-execution runbook. - `USER_STATUS.md` was refreshed with current sync-health snapshot and states that G2 is not authorized. - `AGENT_BOARD.md` keeps G2 Pending and marks T2.1/T8 Done. - Filing freeze references now use `/opt/services/docker-compose.openclaw.yml` and any equivalent website-affecting compose/service entries, instead of relying on the obsolete single `docker-composite.yml` path. - No PC/VPS command was executed, no token was handled, no node was started, no VPS approval was performed, and no service was modified. - Next step: wait for explicit user authorization before opening G2 execution tasks. ## Frozen G0B Summary - QQ is included in the current stage as a primary natural-language entry. - Phone Control UI must be able to start basic tasks, show status/results, and approve high-risk actions. - VPS OpenClaw Gateway is the always-on hub for device connection, routing, approval flow, state aggregation, and audit. - DeepSeek may understand, split, and autonomously trigger white-listed actions. High-risk or non-white-listed actions require human approval. - Windows PC is the main execution node and may perform broad user-level local execution. - PC system-level changes, service installation, network/firewall changes, and large destructive file operations require human approval and rollback notes. - Tailscale is optional for administration, troubleshooting, and private-path enhancement. It is not a G2 prerequisite. - G2/G3/G4 acceptance criteria are recorded in `AGENT_BOARD.md`. ## G2 Planning State - T9: PC foreground node run, draft. - T10: VPS pairing approval, draft. - T11: PC G2 verification, draft. - T12: VPS G2 verification and freeze compliance, draft. - T13: G2 correction guard, draft. - Authorization judgment: prerequisites are sufficient to ask the user whether to authorize G2, but execution must not begin until the user explicitly grants that authorization.