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 16:10:22

Browse Source
This commit is contained in:
wangzhendong
2026-05-15 16:10:22 +08:00
parent d833a900ba
commit 388570ca19
3 changed files with 12 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
AGENT_BOARD.md
View File

@@ -36,7 +36,7 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con
| Gate | Required Evidence | Owner | Status |
|---|---|---|---|
| G0 Requirements aligned | User-approved mission, roles, and acceptance criteria | ORCHESTRATOR | Pending |
| G0 Requirements aligned | User-approved mission, roles, and acceptance criteria | ORCHESTRATOR | Done |
| 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 |

14
handoff/ORCHESTRATOR.md
View File

@@ -21,17 +21,19 @@ 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`.
- G0 is complete: the user confirmed mission, role boundaries, non-mutation rule, communication MVP, freeze policy, and acceptance criteria.
- G1 remains pending until PC_VERIFIER and VPS_VERIFIER accept baseline evidence.
- 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/`.
- Sync-health recovered; T7 is no longer blocked and remains claimed for ongoing CORRECTION monitoring.
- 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 G1 pending until PC_VERIFIER and VPS_VERIFIER accept baseline evidence.
2. Assign or continue PC and VPS read-only baseline tasks in their respective Cursor windows.
3. Require verifier review before any mutation.
4. Keep T7 active for CORRECTION monitoring of sync-health, drift, missing evidence, and freeze-policy risk.
## Open Questions
@@ -41,4 +43,4 @@ Bootstrap the shared Gitea-backed control plane, then coordinate read-only basel
## Last Update
Control-plane repository scaffold prepared locally.
Control-plane status refreshed after `git pull`. G0 is marked complete, G1 remains pending, sync-health is healthy, and no PC/VPS configuration mutation is authorized.

6
sync-state/heartbeat-pc.json
View File

@@ -1,9 +1,9 @@
{
"host": "pc",
"time": "2026-05-15T16:09:20+08:00",
"time": "2026-05-15T16:10:21+08:00",
"branch": "main",
"head": "8c29ed8",
"status": "clean",
"head": "d833a90",
"status": "dirty",
"intervalSeconds": 30,
"heartbeatEverySeconds": 60
}