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:07:36

Browse Source
This commit is contained in:
wangzhendong
2026-05-19 12:07:36 +08:00
parent 1f4364299e
commit cde871f506
3 changed files with 35 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
AGENT_BOARD.md
View File

@@ -23,6 +23,7 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con
- COACH role: the main user-facing chat acts as COACH by default, guiding workflow usability, session freeze, and knowledge capture without replacing ORCHESTRATOR.
- Confirmed OpenClaw target: QQ and phone Control UI are current-stage control entries; the VPS Gateway is the always-on hub; DeepSeek may trigger white-listed actions; Windows PC is the main execution node.
- Tailscale role: optional administration, troubleshooting, and private-path enhancement. It is not a G2 prerequisite; the main path uses the VPS Gateway.
- G2 runbook: `docs/G2_RUNBOOK.md` exists for execution-before-action planning. It does not authorize G2 execution by itself.
- 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
@@ -63,6 +64,11 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con
| 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 |
| 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 |
| T12 | Verify G2 VPS evidence and freeze compliance | VPS_VERIFIER | T10 | Draft |
| T13 | Guard G2 sync, secret, and freeze risks | CORRECTION | User G2 authorization | Draft |
## Confirmed OpenClaw Target Design
@@ -92,6 +98,13 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con
- G3 execution smoke test is accepted only when a harmless task starts from QQ or phone Control UI, routes through the Gateway to the Windows PC, returns visible results, and verifier evidence proves execution came from the PC rather than the VPS.
- G4 persistent service verification is accepted only when the PC node can run as a persistent service or startup item, service install/start/status and reboot survival evidence exist, rollback notes exist for system-level changes, and approval guardrails still work.
## G2 Authorization Boundary
- `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.
## Operating Rules
- Agents must read this file before doing work.

9
USER_STATUS.md
View File

@@ -6,12 +6,13 @@
Stage 1B: OpenClaw target design confirmed.
The collaboration mechanism, target architecture, component boundaries, safety guardrails, and G2/G3/G4 acceptance criteria are now frozen. The system still must not enter connection/setup work until the user explicitly authorizes the next stage.
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.
## 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.
- 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.
@@ -41,13 +42,13 @@ The collaboration mechanism, target architecture, component boundaries, safety g
## Single Recommended Next Step
Wait for explicit user authorization before opening G2 connection setup.
Review `docs/G2_RUNBOOK.md`, then decide whether to explicitly authorize G2 execution.
## User Decision Needed
Not needed immediately.
Yes. The pending decision is whether to authorize G2 execution.
The next decision, when ready, is whether to authorize G2: connect the Windows PC execution node to the VPS OpenClaw Gateway and prepare the QQ/phone control path. That authorization has not been granted yet.
If authorized later, G2 will allow token injection, foreground PC node run, and VPS pairing approval under the runbook guardrails. That authorization has not been granted yet.
## Confirmed Target Design

23
handoff/ORCHESTRATOR.md
View File

@@ -28,15 +28,17 @@ Maintain the shared Gitea-backed control plane, keep user-facing status current,
- 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.
- `docs/G2_RUNBOOK.md` has been prepared as the G2 execution-before-action runbook. It does not authorize execution by itself.
- The polling sync is intentionally temporary; design an async notification/coordinator layer when PC/VPS baseline work is stable.
## Next Actions
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.
1. Ask the user whether to explicitly authorize G2 execution only after they review `docs/G2_RUNBOOK.md`.
2. Keep `USER_STATUS.md` current when gate, blocker, heartbeat, or required user decision changes.
3. Keep T7/CORRECTION monitoring active for sync-health, drift, missing evidence, and freeze-policy risk.
4. If the user authorizes G2 later, move T9-T13 from draft to ready in dependency order and require rollback notes before token/run/approval actions.
5. Track VPS verifier follow-up observations before future mutation: service path naming drift and Nginx route/config anomaly.
6. Do not open G2 or perform Gateway/node pairing until explicitly authorized.
## Open Questions
@@ -45,7 +47,7 @@ Maintain the shared Gitea-backed control plane, keep user-facing status current,
## Last Update
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.
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.
## Frozen G0B Summary
@@ -57,3 +59,12 @@ G0B target design was frozen into `USER_STATUS.md` and `AGENT_BOARD.md`. No PC/V
- 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`.
## G2 Planning State
- T9: PC foreground node run, draft.
- T10: VPS pairing approval, draft.
- T11: PC G2 verification, draft.
- T12: VPS G2 verification and freeze compliance, draft.
- T13: G2 correction guard, draft.
- Authorization judgment: prerequisites are sufficient to ask the user whether to authorize G2, but execution must not begin until the user explicitly grants that authorization.