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 2A Paused: role-misdirection corrected.

G2 planning artifacts exist, but execution is paused after a role-misdirection audit. Do not start the PC node, do not inject a token, and do not approve pairing until ORCHESTRATOR records a fresh explicit user authorization after this correction.

## 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.
- G2 runbook remains available as planning material, but role-misdirection correction paused execution.
- 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-health blocker is recorded.
- G2 execution is blocked by the role-misdirection incident until ORCHESTRATOR restates the next step and the user gives fresh explicit authorization.
- The immediate next phase is role-misdirection hardening, not G2 execution.

## 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 update control-plane status and task files to correct the role-misdirection incident.
- CORRECTION may continue read-only monitoring and keep G2 blocked if evidence or sync state is unsafe.
- COACH/ORCHESTRATOR may update playbooks, recovery procedures, lessons learned, and role-confirmation rules to prevent future misdirected prompts.

## Forbidden Actions

- Do not start Gateway/node pairing or approval outside the T9/T10 sequence in `docs/G2_RUNBOOK.md`.
- Do not run any G2 command outside `docs/G2_RUNBOOK.md`.
- Do not run T9 or T10 while the role-misdirection block is active.
- Do not set or inject `OPENCLAW_GATEWAY_TOKEN`.
- Do not install, start, restart, stop, or persist PC/VPS services.
- Do not run `openclaw node install`, `openclaw node start`, or any service persistence command.
- 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

Complete role-misdirection hardening before asking for any fresh G2 authorization.

## User Decision Needed

Not needed right now. After hardening is complete, a fresh explicit user authorization will be required before any G2 execution can start.

## 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:27 UTC+8 from tracked control-plane files.
- PC sync heartbeat: clean at `2026-05-19T12:26:46+08:00`.
- VPS sync heartbeat: clean at `2026-05-19T12:26:38+0800`.
- Sync error files: none observed.
- G2 runbook: `docs/G2_RUNBOOK.md` complete.
- G2 authorization: paused after role-misdirection audit; fresh explicit authorization required before execution.
- Next work:防误发加固, not G2 execution.
- Public website freeze: still active.
- Mutation/setup phase: not active; all PC node run, token injection, and VPS approval actions are paused.