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:03:55

Browse Source
This commit is contained in:
wangzhendong
2026-05-19 12:03:55 +08:00
parent 2289f6c450
commit 7cd1b08e28
4 changed files with 85 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

39
USER_STATUS.md
View File

@@ -4,13 +4,14 @@
## Current Stage
Stage 1B: Confirm the OpenClaw target design.
Stage 1B: OpenClaw target design confirmed.
The collaboration mechanism is ready, and PC/VPS baseline checks have both been independently accepted. The overall OpenClaw system requirements are not frozen yet, so the system must not enter connection/setup work.
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.
## 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.
- 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.
@@ -20,15 +21,14 @@ The collaboration mechanism is ready, and PC/VPS baseline checks have both been
## Current Blockers
- No active sync blocker is recorded.
- OpenClaw system requirements and target effect are not confirmed yet.
- Connection setup is intentionally paused until the system target and acceptance criteria are frozen.
- Connection setup is intentionally paused because G2 has not been explicitly authorized.
## Allowed Actions
- Keep the sync scripts running.
- Agents may update user-facing status, handoffs, evidence, and internal ledgers.
- Agents may continue read-only monitoring for sync-health, drift, missing evidence, and freeze-policy risk.
- ORCHESTRATOR may discuss and document the OpenClaw target design with the user.
- ORCHESTRATOR may prepare G2 task split and rollback/evidence requirements if the user asks.
## Forbidden Actions
@@ -41,19 +41,30 @@ The collaboration mechanism is ready, and PC/VPS baseline checks have both been
## Single Recommended Next Step
Confirm the OpenClaw target design before any connection/setup work.
Wait for explicit user authorization before opening G2 connection setup.
## User Decision Needed
The user needs to confirm these items:
Not needed immediately.
- Final effect: how phone, PC, and VPS should collaborate through OpenClaw.
- Responsibility boundaries for the VPS Gateway, DeepSeek, and the Docker stack.
- What the Windows PC execution node is allowed to do, and what it must never do.
- Whether Tailscale is optional enhancement or required before setup.
- Phone Control UI access path and acceptance method.
- Whether QQ or other later channels are included now or deferred.
- Concrete acceptance criteria for connection setup, smoke test, and persistent service verification.
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.
## Confirmed Target Design
- QQ is included in the current stage as a primary natural-language entry.
- Phone Control UI must be able to start basic tasks, show status/results, and approve high-risk actions.
- VPS OpenClaw Gateway is the always-on hub for device connection, routing, approval flow, state aggregation, and audit.
- DeepSeek may understand, split, and autonomously trigger white-listed actions. High-risk or non-white-listed actions require human approval.
- Windows PC is the main execution node and may perform broad user-level local execution.
- 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, or private-path enhancement. It is not a G2 prerequisite; the main path uses the VPS Gateway.
- Future multiple PCs, phones, and endpoint model nodes should join through the same Gateway model.
## Frozen Acceptance Criteria
- G2 connection setup is accepted only when the PC node can connect to the VPS Gateway, the VPS can show pending/approved node state, approval does not leak secrets, and the frozen `smartmotor.cloud` website output remains unchanged.
- G3 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 persistence 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.
## Latest Health Snapshot