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

Sync agent state from VPS at 2026-05-19 12:11:54

Browse Source
This commit is contained in:
ubuntu
2026-05-19 12:11:54 +08:00
parent 8999b2b7c1
commit cb466a820d
3 changed files with 27 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
AGENT_BOARD.md
View File

@@ -1,6 +1,6 @@
# OpenClaw Agent Control Board
> Source of truth for multi-agent work across the Windows PC workspace and the VPS `/opt/service` workspace.
> Source of truth for multi-agent work across the Windows PC workspace and the VPS `/opt/services` workspace.
## Mission
@@ -16,7 +16,7 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con
- PC control-plane path: `D:\openclaw-control-plane`.
- VPS control-plane path: `/home/ubuntu/openclaw-control-plane`.
- Secrets policy: no password, token, API key, or `OPENCLAW_GATEWAY_TOKEN` may be written into repo files, handoffs, evidence, or chat.
- Frozen website policy: strict freeze during ICP/public-security filing review. Agents must not change the `smartmotor.cloud` homepage, content reachable from homepage links, static assets, Nginx routing, bind mounts, container images, or `/opt/services/docker-composite.yml` entries that could alter public website output.
- Frozen website policy: strict freeze during ICP/public-security filing review. Agents must not change the `smartmotor.cloud` homepage, content reachable from homepage links, static assets, Nginx routing, bind mounts, container images, `/opt/services/docker-compose.openclaw.yml`, or any equivalent compose/service entries that could alter public website output.
- Communication MVP: use Git-backed polling sync scripts under `sync/` plus task files under `tasks/`. This reduces manual pull/push but is not the final async-notification design.
- Sync-health monitoring: CORRECTION monitors tracked heartbeat and error files under `sync-state/`; no separate sync monitor agent is used at this stage.
- User-facing status entry: `USER_STATUS.md`. Users should not need to read internal task, handoff, evidence, or sync-state files for routine status.
@@ -32,7 +32,7 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con
|---|---|---|
| ORCHESTRATOR | Requirements alignment, task split, dependency tracking, final acceptance | `AGENT_BOARD.md`, `handoff/ORCHESTRATOR.md` |
| PC_EXECUTOR | Windows PC, Tailscale, OpenClaw CLI/node, local service install | `handoff/PC_EXECUTOR.md`, `evidence/pc-*`, `rollback/pc-*` |
| VPS_EXECUTOR | VPS `/opt/service`, Gateway, Docker stack, Nginx, Gitea, approvals | `handoff/VPS_EXECUTOR.md`, `evidence/vps-*`, `rollback/vps-*` |
| VPS_EXECUTOR | VPS `/opt/services`, Gateway, Docker stack, Nginx, Gitea, approvals | `handoff/VPS_EXECUTOR.md`, `evidence/vps-*`, `rollback/vps-*` |
| PC_VERIFIER | Independent read-only validation of PC executor results | `handoff/PC_VERIFIER.md`, `evidence/verify-pc-*` |
| VPS_VERIFIER | Independent read-only validation of VPS executor results | `handoff/VPS_VERIFIER.md`, `evidence/verify-vps-*` |
| CORRECTION | Detect drift, sync-health failures, conflicts, unsafe changes, missing evidence, and rollback needs | `handoff/CORRECTION.md`, `tasks/T7-correction-monitor.md` |
@@ -57,13 +57,13 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con
| T0 | Create local control-plane scaffold | ORCHESTRATOR | None | Done |
| T1 | Create standalone Gitea repo for this control plane | User + ORCHESTRATOR | T0 | Done |
| T2 | Sync this scaffold to Gitea and open on PC/VPS Cursor | ORCHESTRATOR + VPS_EXECUTOR | T1 | Done |
| T2.1 | Add polling sync and task-file communication MVP | ORCHESTRATOR | T2 | In Progress |
| T2.1 | Add polling sync and task-file communication MVP | ORCHESTRATOR | T2 | Done |
| T3 | Run read-only PC baseline discovery | PC_EXECUTOR | T2.1 | Accepted |
| T4 | Run read-only VPS baseline discovery | VPS_EXECUTOR | T2.1 | Accepted |
| T5 | Verify PC baseline before any PC change | PC_VERIFIER | T3 | Accepted |
| T6 | Verify VPS baseline before any VPS change | VPS_VERIFIER | T4 | Accepted |
| T7 | Monitor drift, sync-health failures, conflicts, unsafe changes, and missing evidence | CORRECTION | G0A | Claimed |
| T8 | Solidify COACH role, session freeze, and knowledge capture | COACH | T2.1 | In Progress |
| T8 | Solidify COACH role, session freeze, and knowledge capture | COACH | T2.1 | Done |
| T9 | G2 PC foreground node run | PC_EXECUTOR | User G2 authorization, T7 healthy | Draft |
| T10 | G2 VPS pairing approval | VPS_EXECUTOR | T9, explicit approval authorization | Draft |
| T11 | Verify G2 PC evidence | PC_VERIFIER | T9 | Draft |
@@ -103,14 +103,14 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con
- `docs/G2_RUNBOOK.md` and T9-T13 are planning artifacts only while G2 is pending.
- G2 requires explicit user authorization before token injection, `openclaw node run`, VPS pairing approval, or any executor action.
- G2 must remain foreground-only for the PC node; service persistence belongs to G4.
- G2 must not change the frozen `smartmotor.cloud` homepage, homepage-linked content, static assets, Nginx routing, Docker bind mounts, container images, or website-affecting compose entries.
- G2 must not change the frozen `smartmotor.cloud` homepage, homepage-linked content, static assets, Nginx routing, Docker bind mounts, container images, `/opt/services/docker-compose.openclaw.yml`, or any equivalent website-affecting compose/service entries.
## Operating Rules
- Agents must read this file before doing work.
- Executors must not accept work outside their named scope.
- Executors must not validate their own work as complete.
- VPS-related agents must treat the `smartmotor.cloud` website defined by `/opt/services/docker-composite.yml` as frozen: no edits to homepage content, linked page content, routing, static assets, bind mounts, container images, or Nginx rules that could alter what public visitors see.
- VPS-related agents must treat the `smartmotor.cloud` website and related service definitions as frozen during filing review: no edits to homepage content, linked page content, routing, static assets, bind mounts, container images, Nginx rules, `/opt/services/docker-compose.openclaw.yml`, or any equivalent compose/service entries that could alter what public visitors see.
- Polling sync scripts are convenience automation only. If they report conflict, authentication failure, or unexpected files, stop and let CORRECTION review.
- Sync scripts must publish non-secret heartbeat/error status under `sync-state/`. Heartbeat older than 2 minutes is warning; older than 5 minutes is blocked.
- Task files under `tasks/` are the agent-to-agent work contract. Chat messages are not the source of truth.

14
USER_STATUS.md
View File

@@ -4,19 +4,20 @@
## Current Stage
Stage 1B: OpenClaw target design confirmed.
Stage 1C: G2 authorization-ready, execution not authorized.
The collaboration mechanism, target architecture, component boundaries, safety guardrails, and G2/G3/G4 acceptance criteria are frozen. A G2 execution-before-action runbook now exists at `docs/G2_RUNBOOK.md`, but the system still must not enter connection/setup work until the user explicitly authorizes G2.
The collaboration mechanism, target architecture, component boundaries, safety guardrails, and G2/G3/G4 acceptance criteria are frozen. `docs/G2_RUNBOOK.md` is complete for G2 execution-before-action planning, but the system must not enter connection/setup work until the user explicitly authorizes G2.
## Completed
- Collaboration mechanism was confirmed: agent roles, Git polling MVP, sync-health monitoring, and this user-facing status page.
- OpenClaw target design was confirmed: QQ and phone Control UI are control entries, VPS Gateway is the always-on hub, DeepSeek handles white-listed autonomous decisions, and Windows PC is the main execution node.
- G2 runbook and draft role tasks were prepared for review.
- `docs/G2_RUNBOOK.md` was completed as the G2 pre-execution plan.
- The `smartmotor.cloud` filing-review website freeze is active as a hard rule.
- PC baseline was collected and independently accepted.
- VPS baseline was collected and independently accepted.
- Sync-health recovered and is currently monitored by CORRECTION.
- Sync-health recovered and is currently healthy under CORRECTION monitoring.
- Current communication remains Git polling; future work should upgrade to async notification or a coordinator after the basic path is stable.
## Current Blockers
@@ -69,8 +70,11 @@ If authorized later, G2 will allow token injection, foreground PC node run, and
## Latest Health Snapshot
- PC sync heartbeat: clean at `2026-05-15T16:21:44+08:00`.
- VPS sync heartbeat: clean at `2026-05-15T16:20:51+0800`.
- Snapshot refreshed: 2026-05-19 12:11 UTC+8 from tracked control-plane files.
- PC sync heartbeat: clean at `2026-05-19T12:10:11+08:00`.
- VPS sync heartbeat: clean at `2026-05-19T12:10:22+0800`.
- Sync error files: none observed.
- G2 runbook: `docs/G2_RUNBOOK.md` complete.
- G2 authorization: not granted.
- Public website freeze: still active.
- Mutation/setup phase: not started.

12
handoff/ORCHESTRATOR.md
View File

@@ -29,7 +29,10 @@ Maintain the shared Gitea-backed control plane, keep user-facing status current,
- `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.
- 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
@@ -47,7 +50,14 @@ Maintain the shared Gitea-backed control plane, keep user-facing status current,
## 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.
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