From ba1b97c4e71cde707a6f64d6a82d3f00cefd31b1 Mon Sep 17 00:00:00 2001 From: wangzhendong Date: Tue, 19 May 2026 12:35:38 +0800 Subject: [PATCH] Sync agent state from PC at 2026-05-19 12:35:38 --- USER_STATUS.md | 7 +++--- docs/G2_AUTHORIZATION_CARD.md | 45 +++++++++++++++++++++++++++++++++++ handoff/ORCHESTRATOR.md | 16 +++++++++---- 3 files changed, 61 insertions(+), 7 deletions(-) create mode 100644 docs/G2_AUTHORIZATION_CARD.md diff --git a/USER_STATUS.md b/USER_STATUS.md index 5c2a9f6..4edba33 100644 --- a/USER_STATUS.md +++ b/USER_STATUS.md @@ -50,11 +50,11 @@ G2 planning artifacts exist, but execution is paused after a role-misdirection a ## Single Recommended Next Step -Complete role-misdirection hardening before asking for any fresh G2 authorization. +Review `docs/G2_AUTHORIZATION_CARD.md`. If ready, copy its second authorization statement into the ORCHESTRATOR window. ## 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. +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. ## Confirmed Target Design @@ -80,7 +80,8 @@ Not needed right now. After hardening is complete, a fresh explicit user authori - 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 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:防误发加固, not G2 execution. +- Next work: user review of the authorization card, not G2 execution yet. - Public website freeze: still active. - Mutation/setup phase: not active; all PC node run, token injection, and VPS approval actions are paused. diff --git a/docs/G2_AUTHORIZATION_CARD.md b/docs/G2_AUTHORIZATION_CARD.md new file mode 100644 index 0000000..4a94453 --- /dev/null +++ b/docs/G2_AUTHORIZATION_CARD.md @@ -0,0 +1,45 @@ +# G2 Authorization Card + +## Confirmation + +- Current target window: ORCHESTRATOR. +- Current workspace: `D:\openclaw-control-plane`. +- G2 current state: paused/pending. +- Old G2 authorization: not valid after the role-misdirection correction. +- Sync-health: healthy by tracked files. +- PC heartbeat: `clean` at `2026-05-19T12:35:06+08:00`. +- VPS heartbeat: `clean` at `2026-05-19T12:34:45+0800`. +- Sync error files: none observed. + +## What This Card Does + +This card gives the user one exact second authorization statement to copy when ready. + +It does not execute G2 by itself. It does not authorize any agent to proceed unless the statement is sent by the user to the ORCHESTRATOR window after reviewing this card. + +## Copyable Second Authorization Statement + +```text +目标窗口：ORCHESTRATOR +当前工作区：D:\openclaw-control-plane + +我确认这是 role-misdirection 修正后的第二段 G2 授权。 + +授权范围：仅 G2。 + +允许动作：按 docs/G2_RUNBOOK.md 打开 T9/T10；允许 PC_EXECUTOR 执行前台 PC node run；允许 VPS_EXECUTOR 在 T9 产生匹配的非 secret pairing request/node ID 后执行对应 VPS pairing approval。 + +禁止动作：不得执行 openclaw node install/start/persistence；不得进行服务重启；不得修改 Nginx/Docker/网站/防火墙/网络；不得记录、打印、提交、写入或聊天发送任何 secret、token、password、API key、private key、cookie 或 OPENCLAW_GATEWAY_TOKEN。 + +授权失效条件：sync blocked；目标角色不匹配；当前工作区不匹配；出现或可能记录 secret；出现多个或不明确的 pairing request；任何步骤偏离 docs/G2_RUNBOOK.md；任何动作可能影响 smartmotor.cloud 备案冻结网站输出。 +``` + +## ORCHESTRATOR Handling Rules After Copy + +If the user sends the authorization statement above: + +- Confirm target role and workspace again before changing task status. +- Move only the eligible G2 guard/task statuses needed to begin the runbook. +- Keep service persistence, G3 smoke test, and G4 service installation closed. +- Require rollback notes before token use, foreground node run, and approval actions. +- Stop immediately if any invalidation condition appears. diff --git a/handoff/ORCHESTRATOR.md b/handoff/ORCHESTRATOR.md index 86ca58b..043ebe6 100644 --- a/handoff/ORCHESTRATOR.md +++ b/handoff/ORCHESTRATOR.md @@ -37,10 +37,11 @@ Correct the control plane after a role-misdirection incident, keep G2 paused, an ## Next Actions 1. Keep T9/T10/T13 blocked and do not allow token injection, foreground node run, or VPS pairing approval. -2. Keep `USER_STATUS.md` current when gate, blocker, heartbeat, or required user decision changes. -3. Keep T7/CORRECTION monitoring active for sync-health, drift, missing evidence, and freeze-policy risk. -4. If the user later gives fresh explicit G2 authorization, move T13 then T9 to ready, keep T10 blocked until T9 evidence includes a matching non-secret pairing request ID or pending node ID, and require rollback notes before any token/run/approval action. -5. Continue forbidding service persistence, `openclaw node install/start`, Nginx/Docker/website changes, firewall/network changes, and recording any token or secret. +2. Ask the user to review `docs/G2_AUTHORIZATION_CARD.md` if they want to start G2. +3. Keep `USER_STATUS.md` current when gate, blocker, heartbeat, or required user decision changes. +4. Keep T7/CORRECTION monitoring active for sync-health, drift, missing evidence, and freeze-policy risk. +5. If the user sends the exact second authorization statement from `docs/G2_AUTHORIZATION_CARD.md`, confirm role/workspace again, then move T13 and T9 in dependency order; keep T10 blocked until T9 evidence includes a matching non-secret pairing request ID or pending node ID. +6. Continue forbidding service persistence, `openclaw node install/start`, Nginx/Docker/website changes, firewall/network changes, and recording any token or secret. ## Open Questions @@ -56,6 +57,13 @@ Correct the control plane after a role-misdirection incident, keep G2 paused, an - ORCHESTRATOR adopts `docs/G2_RUNBOOK.md` as planning material only, but corrects the active state: G2 is Pending, T9/T10/T13 are blocked, and fresh explicit user authorization is required before any G2 execution. - No PC/VPS command was executed by ORCHESTRATOR during this correction. +2026-05-19 12:34 UTC+8: Generated `docs/G2_AUTHORIZATION_CARD.md`. + +- Confirmed current target role is ORCHESTRATOR and workspace is `D:\openclaw-control-plane`. +- Confirmed G2 is paused/pending and old authorization must not be reused. +- Confirmed tracked sync-health is healthy: PC and VPS heartbeats are clean and no `sync-state/error-*.md` files were observed. +- No PC/VPS command was executed, no token was handled, no node was started, and no VPS approval was performed. + 2026-05-19 12:16 UTC+8: Prior G2 authorization record is superseded by the 12:27 role-misdirection correction. - Previously recorded allowed scope: foreground PC node run and corresponding VPS pairing approval under `docs/G2_RUNBOOK.md`.