wangzhendong/openclaw-control-plane
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Sync agent state from PC at 2026-05-19 12:03:55

Browse Source
This commit is contained in:
wangzhendong
2026-05-19 12:03:55 +08:00
parent 2289f6c450
commit 7cd1b08e28
4 changed files with 85 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

35
handoff/ORCHESTRATOR.md
View File

@@ -6,7 +6,7 @@ Own requirements alignment, task decomposition, dependency tracking, and final a
## Current Objective
Bootstrap the shared Gitea-backed control plane, then coordinate read-only baseline discovery on PC and VPS.
Maintain the shared Gitea-backed control plane, keep user-facing status current, and coordinate the next gate only after explicit user authorization.
## Must Read
@@ -21,24 +21,39 @@ Bootstrap the shared Gitea-backed control plane, then coordinate read-only basel
- 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.
- The polling sync is intentionally temporary; design an async notification/coordinator layer when PC/VPS baseline work is stable.
## Next Actions
1. Commit and push the communication MVP files to Gitea.
2. Ask the user to start or approve starting one sync script on PC and one on VPS.
3. Run G0 requirements and acceptance review with the user.
4. Assign PC and VPS read-only baseline tasks in their respective Cursor windows.
5. Require verifier review before any mutation.
1. Keep `USER_STATUS.md` current when gate, blocker, heartbeat, or required user decision changes.
2. Keep T7/CORRECTION monitoring active for sync-health, drift, missing evidence, and freeze-policy risk.
3. If the user authorizes G2 later, split G2 into executor/verifier tasks with rollback notes and evidence requirements before any mutation.
4. Track VPS verifier follow-up observations before future mutation: service path naming drift and Nginx route/config anomaly.
5. Do not open G2 or perform Gateway/node pairing until explicitly authorized.
## 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?
- 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
Control-plane repository scaffold prepared locally.
G0B target design was frozen into `USER_STATUS.md` and `AGENT_BOARD.md`. No PC/VPS configuration mutation 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`.