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:16:04

Browse Source
This commit is contained in:
wangzhendong
2026-05-15 16:16:04 +08:00
parent 8b099e686e
commit 6e5ec23fff
6 changed files with 26 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
AGENT_BOARD.md
View File

@@ -37,7 +37,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 | Done |
| G1 Baseline discovered | PC and VPS read-only status snapshots | PC_EXECUTOR, VPS_EXECUTOR, verifiers | Pending |
| G1 Baseline discovered | PC and VPS read-only status snapshots accepted by independent verifiers | PC_EXECUTOR, VPS_EXECUTOR, verifiers | Done |
| 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 |
| G4 Persistent service verified | `node install/start/status` and reboot survival evidence | PC_VERIFIER, CORRECTION | Pending |
@@ -51,9 +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 | 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 |
| 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 | G0 | Claimed |
## Acceptance Criteria Draft

12
handoff/ORCHESTRATOR.md
View File

@@ -22,18 +22,18 @@ Bootstrap the shared Gitea-backed control plane, then coordinate read-only basel
- 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.
- G1 baseline is complete: PC_VERIFIER accepted T5 and VPS_VERIFIER accepted T6.
- 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.
- Mutation-stage work is still not authorized in this session.
- The polling sync is intentionally temporary; design an async notification/coordinator layer when PC/VPS baseline work is stable.
## Next Actions
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.
1. Keep T7 active for CORRECTION monitoring of sync-health, drift, missing evidence, and freeze-policy risk.
2. Track the VPS verifier follow-up observations before any future mutation task: service path naming drift and Nginx route/config anomaly.
3. Do not open G2 or any mutation-stage task until explicitly authorized.
## Open Questions
@@ -43,4 +43,4 @@ Bootstrap the shared Gitea-backed control plane, then coordinate read-only basel
## Last Update
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.
Control-plane status refreshed after `git pull`. G0 and G1 are marked complete based on PC/VPS verifier acceptance. Sync-health is healthy, T7 remains claimed, and no PC/VPS configuration mutation is authorized.

2
tasks/T3-PC-baseline.md
View File

@@ -2,7 +2,7 @@
## Status
ready
accepted
## Owner

2
tasks/T4-VPS-baseline.md
View File

@@ -2,7 +2,7 @@
## Status
ready
accepted
## Owner

10
tasks/T6-VPS-baseline-verify.md
View File

@@ -2,7 +2,15 @@
## Status
draft
accepted
## Review Result - 2026-05-15
- Reviewed `evidence/vps-baseline-20260515.md` and recorded independent verification in `evidence/verify-vps-baseline-20260515.md`.
- Accepted the VPS half of G1 with follow-up observations, not blockers.
- Confirmed no approval, restart, reload, token rotation, Nginx route edit, Docker compose edit, bind mount change, image change, or service-state mutation was performed.
- Confirmed the `smartmotor.cloud` filing-review freeze was not touched during T4/T6 baseline review.
- Follow-up observations to track before future mutation: `/opt/service` versus `/opt/services`, `docker-composite.yml` versus `docker-compose.openclaw.yml`, and the Nginx route/config anomaly where endpoints respond but mounted/generated route output did not show expected server blocks.
## Owner

5
tasks/T7-correction-monitor.md
View File

@@ -29,9 +29,10 @@ This task does not authorize PC or VPS configuration mutation. CORRECTION may bl
## Monitoring Findings
- 2026-05-15 16:03 UTC+8: Re-ran sync-health after `git pull`. `sync-state/heartbeat-pc.json` and `sync-state/heartbeat-vps.json` both exist, both report `clean`, and both were under 5 minutes old at check time. No `sync-state/error-*.md` files were present. Sync-health blocked state is cleared; T7 remains `claimed` for ongoing CORRECTION monitoring.
- 2026-05-15 16:14 UTC+8: ORCHESTRATOR refreshed after `git pull`; repository was already up to date. `sync-state/heartbeat-pc.json` and `sync-state/heartbeat-vps.json` both report `clean`, and no `sync-state/error-*.md` files are present. PC baseline and VPS baseline have both been accepted by independent verifiers, so G1 can be treated as complete. Mutation-stage work remains unauthorized in this session.
- 2026-05-15 11:42 UTC+8: Read `AGENT_BOARD.md`, `README.md`, `.cursor/rules/agent-orchestration.mdc`, this task, and all relevant PC/VPS handoffs and baseline tasks.
- Current state: T3/T4 are `ready`, T5/T6 are `draft`, and G1 remains pending.
- Evidence state: only `evidence/README.md` exists; no PC/VPS baseline or verifier evidence exists yet.
- Current state: T3/T4/T5/T6 are `accepted`; T7 remains `claimed`.
- Evidence state: PC baseline, VPS baseline, and VPS verifier evidence are present. PC verifier acceptance is recorded in `tasks/T5-PC-baseline-verify.md` and `handoff/PC_VERIFIER.md`.
- No executor overreach, frozen `smartmotor.cloud` website mutation, pre-G1 configuration mutation, rollback-note gap, sync conflict, or secret-bearing evidence was detected in tracked repository contents.
- Correction decision: no task is blocked in this pass, but no PC/VPS mutation-stage work is authorized until G1 is independently verified and accepted.