# ORCHESTRATOR Handoff

## Role

Own requirements alignment, task decomposition, dependency tracking, and final acceptance.

## Current Objective

Maintain the shared Gitea-backed control plane, keep user-facing status current, and coordinate the next gate only after explicit user authorization.

## 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 and mutation-stage work are not authorized until the user explicitly opens the next stage.
- `docs/G2_RUNBOOK.md` has been prepared as the G2 execution-before-action runbook. It does not authorize execution by itself.
- The polling sync is intentionally temporary; design an async notification/coordinator layer when PC/VPS baseline work is stable.

## Next Actions

1. Ask the user whether to explicitly authorize G2 execution only after they review `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. If the user authorizes G2 later, move T9-T13 from draft to ready in dependency order and require rollback notes before token/run/approval actions.
5. Track VPS verifier follow-up observations before future mutation: service path naming drift and Nginx route/config anomaly.
6. Do not open G2 or perform Gateway/node pairing until explicitly authorized.

## 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

Prepared `docs/G2_RUNBOOK.md` and draft G2 tasks T9-T13. No PC/VPS command was executed, no token was handled, no node was started, no VPS approval was performed, and G2 remains closed until explicit user authorization.

## 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.