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-15 12:08:33

Browse Source
This commit is contained in:
wangzhendong
2026-05-15 12:08:33 +08:00
parent dd420a5030
commit 13dfa12d73
5 changed files with 42 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
AGENT_BOARD.md
View File

@@ -18,6 +18,7 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con
- 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.
- 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.
- Future communication target: when the baseline path is stable, design an event-driven coordinator using Gitea webhooks, Gitea Issues, OpenClaw events, or Cursor SDK agent orchestration.
## Agent Roles
@@ -29,13 +30,13 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con
| VPS_EXECUTOR | VPS `/opt/service`, 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, conflicts, unsafe changes, missing evidence, and rollback needs | `handoff/CORRECTION.md` |
| CORRECTION | Detect drift, sync-health failures, conflicts, unsafe changes, missing evidence, and rollback needs | `handoff/CORRECTION.md`, `tasks/T7-correction-monitor.md` |
## Quality Gates
| Gate | Required Evidence | Owner | Status |
|---|---|---|---|
| G0 Requirements aligned | User-approved mission, roles, boundaries, communication MVP, freeze rule, and acceptance criteria | ORCHESTRATOR | Done |
| G0 Requirements aligned | User-approved mission, roles, and acceptance criteria | ORCHESTRATOR | Pending |
| G1 Baseline discovered | PC and VPS read-only status snapshots | PC_EXECUTOR, VPS_EXECUTOR, verifiers | Pending |
| G2 Gateway/node pairing ready | PC `node run` evidence and VPS approval evidence | PC_EXECUTOR, VPS_EXECUTOR | Pending |
| G3 Execution smoke test | Harmless command result proves execution came from the PC node | PC_VERIFIER | Pending |
@@ -50,13 +51,11 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con
| 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 |
| T3 | Run read-only PC baseline discovery | PC_EXECUTOR | G0, T2.1 | Ready |
| T4 | Run read-only VPS baseline discovery | VPS_EXECUTOR | G0, T2.1 | Ready |
| T5 | Verify PC baseline before any PC change | PC_VERIFIER | T3 | Pending |
| T6 | Verify VPS baseline before any VPS change | VPS_VERIFIER | T4 | Pending |
| T7 | Monitor drift, conflicts, unsafe changes, and missing evidence | CORRECTION | G0 | Ready |
| T3 | Run read-only PC baseline discovery | PC_EXECUTOR | T2.1 | Ready |
| T4 | Run read-only VPS baseline discovery | VPS_EXECUTOR | T2.1 | Ready |
| T5 | Verify both baselines before any config change | PC_VERIFIER + VPS_VERIFIER | T3, T4 | Pending |
## Acceptance Criteria
## Acceptance Criteria Draft
- The PC can act as an OpenClaw execution node connected to the existing Gateway.
- The Gateway continues to coexist with Nginx, Gitea, Confluence, and Postgres on the VPS.
@@ -65,8 +64,6 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con
- Tailscale is optional for the OpenClaw public Gateway path, but available for safer device-to-device operations.
- Phone can be used as a control client after the execution path is stable.
- Later QQ or other channels are added only after the Gateway/node path is verified.
- Before verified G1 baseline completion, executors may perform only read-only discovery and evidence capture.
- The current communication layer is the Git polling MVP under `sync/` plus task files under `tasks/`; after the baseline path is stable, it must be upgraded or supplemented with asynchronous notification or a coordinator.
## Operating Rules
@@ -75,6 +72,7 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con
- 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.
- 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.
- Any system-level change requires a rollback note before execution.
- Any blocking issue must be recorded in the relevant handoff file and surfaced to ORCHESTRATOR.