openclaw-control-plane/USER_STATUS.md

OpenClaw User Status

This is the user-facing status page. Agent board, task files, handoffs, evidence, and sync-state files are internal agent ledgers.

Current Stage

Stage 1C: G2 authorization-ready, execution not authorized.

The collaboration mechanism, target architecture, component boundaries, safety guardrails, and G2/G3/G4 acceptance criteria are frozen. docs/G2_RUNBOOK.md is complete for G2 execution-before-action planning, but the system 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.
• docs/G2_RUNBOOK.md was completed as the G2 pre-execution plan.
• 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.
• Sync-health recovered and is currently healthy under CORRECTION monitoring.
• Current communication remains Git polling; future work should upgrade to async notification or a coordinator after the basic path is stable.

Current Blockers

• No active sync blocker is recorded.
• 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 prepare G2 task split and rollback/evidence requirements if the user asks.

Forbidden Actions

• Do not start Gateway/node pairing or approval.
• Do not run PC node setup commands.
• Do not install, start, restart, stop, or persist PC/VPS services.
• Do not change firewall, routing, Nginx, Docker compose, bind mounts, container images, environment variables, or service state.
• Do not change the smartmotor.cloud homepage, linked content, static assets, routing, or anything that could alter public website output during filing review.
• Do not write secrets, tokens, passwords, API keys, private keys, cookies, or OPENCLAW_GATEWAY_TOKEN into files, logs, evidence, commits, or chat.

Single Recommended Next Step

Review docs/G2_RUNBOOK.md, then decide whether to explicitly authorize G2 execution.

User Decision Needed

Yes. The pending decision is whether to authorize G2 execution.

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

• 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

• Snapshot refreshed: 2026-05-19 12:11 UTC+8 from tracked control-plane files.
• PC sync heartbeat: clean at 2026-05-19T12:10:11+08:00.
• VPS sync heartbeat: clean at 2026-05-19T12:10:22+0800.
• Sync error files: none observed.
• G2 runbook: docs/G2_RUNBOOK.md complete.
• G2 authorization: not granted.
• Public website freeze: still active.
• Mutation/setup phase: not started.