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 17:06:56

Browse Source
This commit is contained in:
wangzhendong
2026-05-19 17:06:57 +08:00
parent a87e03456e
commit 21b1a1f988
4 changed files with 47 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
USER_STATUS.md
View File

@@ -6,7 +6,7 @@
Stage 2A Authorized: foreground G2 may start under runbook.
Fresh second G2 authorization was reconfirmed for ORCHESTRATOR in `D:\openclaw-control-plane`. CORRECTION recorded a fresh T13 PASS, so 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.
Fresh second G2 authorization was reconfirmed for ORCHESTRATOR in `D:\openclaw-control-plane`. CORRECTION recorded a fresh T13 PASS, so T9 may proceed under `docs/G2_RUNBOOK.md` using a user-run local PowerShell token/node flow; T10 must wait until T9 produces a matching non-secret pairing request ID or pending node ID.
## Completed
@@ -34,7 +34,7 @@ Fresh second G2 authorization was reconfirmed for ORCHESTRATOR in `D:\openclaw-c
- 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.
- 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`.
- PC_EXECUTOR may claim T9, confirm or refresh the required rollback note, give the user the dedicated local PowerShell command template, and collect only non-secret status from the user-run 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
@@ -42,7 +42,8 @@ Fresh second G2 authorization was reconfirmed for ORCHESTRATOR in `D:\openclaw-c
- 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 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 record, print, commit, or chat-send `OPENCLAW_GATEWAY_TOKEN`; token may only be set by the user in a dedicated local PC PowerShell terminal during T9.
- PC_EXECUTOR must not receive the token, paste it into an Agent shell, or run the token-bearing foreground node flow directly.
- 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.
@@ -51,7 +52,7 @@ Fresh second G2 authorization was reconfirmed for ORCHESTRATOR in `D:\openclaw-c
## Single Recommended Next Step
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`.
PC_EXECUTOR should claim T9, confirm or refresh `rollback/pc-g2-node-run-YYYYMMDD.md`, give the user the dedicated local PowerShell command template, and collect only non-secret status from the user-run foreground node flow in `docs/G2_RUNBOOK.md`.
## User Decision Needed
@@ -83,7 +84,7 @@ No additional user decision is needed for T9 if PC_EXECUTOR stays within `docs/G
- G2 runbook: `docs/G2_RUNBOOK.md` complete.
- G2 authorization card: `docs/G2_AUTHORIZATION_CARD.md` prepared for user review.
- G2 authorization: fresh second authorization reconfirmed for foreground PC node run and corresponding VPS pairing approval only.
- Next work: T9 foreground PC node run by PC_EXECUTOR.
- Next work: T9 user-run foreground PC node flow guided by PC_EXECUTOR.
- Public website freeze: still active.
- Mutation/setup phase: limited G2 foreground pairing may start; service persistence and infrastructure changes remain forbidden.
@@ -95,4 +96,4 @@ No additional user decision is needed for T9 if PC_EXECUTOR stays within `docs/G
- Blocked: T10/VPS approval until T9 produces one matching non-secret pairing request/node ID. G3 and G4 remain closed.
- Safety constraints: no secret recording, no `openclaw node install/start`, no service persistence, no Nginx/Docker/website/firewall/network changes.
- Next owner: PC_EXECUTOR for T9, with CORRECTION monitoring T13.
- Single next action: PC_EXECUTOR claims T9, confirms or refreshes `rollback/pc-g2-node-run-YYYYMMDD.md`, then follows only the foreground node flow in `docs/G2_RUNBOOK.md`.
- Single next action: PC_EXECUTOR claims T9, confirms or refreshes `rollback/pc-g2-node-run-YYYYMMDD.md`, gives the user the dedicated local PowerShell command template, then records only non-secret status from the user-run foreground node flow in `docs/G2_RUNBOOK.md`.