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:38:46

Browse Source
This commit is contained in:
wangzhendong
2026-05-19 12:38:46 +08:00
parent 2f83a21e14
commit 50d271318d
5 changed files with 33 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
USER_STATUS.md
View File

@@ -4,9 +4,9 @@
## Current Stage
Stage 2A Paused: role-misdirection corrected.
Stage 2A Authorized: foreground G2 may start under runbook.
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.
Fresh second G2 authorization was received for ORCHESTRATOR in `D:\openclaw-control-plane`. T13 and T9 may proceed under `docs/G2_RUNBOOK.md`; T10 must wait until T9 produces a matching non-secret pairing request ID or pending node ID.
## Completed
@@ -14,7 +14,8 @@ G2 planning artifacts exist, but execution is paused after a role-misdirection a
- 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.
- G2 runbook remains the binding procedure for this limited foreground pairing stage.
- Fresh second G2 authorization was recorded for ORCHESTRATOR after role-misdirection correction.
- 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.
@@ -24,24 +25,24 @@ G2 planning artifacts exist, but execution is paused after a role-misdirection a
## 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.
- VPS pairing approval is blocked until T9 produces a matching non-secret pairing request ID or pending node ID.
- G3 smoke test and G4 persistence remain closed.
## 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.
- CORRECTION may monitor T13 for sync, secret, role, and freeze risks.
- PC_EXECUTOR may claim T9, write the required rollback note, set the Gateway token only in the local shell/session without recording it, and run only the foreground PC node flow in `docs/G2_RUNBOOK.md`.
- VPS_EXECUTOR may not act yet; T10 waits for T9 evidence with a matching non-secret pairing request/node ID.
## 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 run T10 until T9 produces a matching non-secret pairing request/node ID.
- Do not record, print, commit, or chat-send `OPENCLAW_GATEWAY_TOKEN`; token may only be set locally by PC_EXECUTOR within T9.
- 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.
@@ -50,11 +51,11 @@ G2 planning artifacts exist, but execution is paused after a role-misdirection a
## Single Recommended Next Step
Review `docs/G2_AUTHORIZATION_CARD.md`. If ready, copy its second authorization statement into the ORCHESTRATOR window.
PC_EXECUTOR should claim T9, write `rollback/pc-g2-node-run-YYYYMMDD.md`, and follow only the foreground node flow in `docs/G2_RUNBOOK.md`.
## User Decision Needed
Yes, but only if the user wants to start G2. Use the exact second authorization statement in `docs/G2_AUTHORIZATION_CARD.md`; old authorization remains invalid.
No additional user decision is needed for T9 if PC_EXECUTOR stays within `docs/G2_RUNBOOK.md`. A new decision is required for G3 smoke test, G4 persistence, service changes, network/firewall changes, Nginx/Docker/website changes, or any action outside the runbook.
## Confirmed Target Design
@@ -81,7 +82,7 @@ Yes, but only if the user wants to start G2. Use the exact second authorization
- Sync error files: none observed.
- G2 runbook: `docs/G2_RUNBOOK.md` complete.
- G2 authorization card: `docs/G2_AUTHORIZATION_CARD.md` prepared for user review.
- G2 authorization: paused after role-misdirection audit; fresh explicit authorization required before execution.
- Next work: user review of the authorization card, not G2 execution yet.
- G2 authorization: fresh second authorization recorded for foreground PC node run and corresponding VPS pairing approval only.
- Next work: T13 guard and T9 foreground PC node run.
- Public website freeze: still active.
- Mutation/setup phase: not active; all PC node run, token injection, and VPS approval actions are paused.
- Mutation/setup phase: limited G2 foreground pairing may start; service persistence and infrastructure changes remain forbidden.