From 1400aea06018fe9b748677b51d4ff76c655c5728 Mon Sep 17 00:00:00 2001 From: ubuntu Date: Tue, 19 May 2026 12:16:58 +0800 Subject: [PATCH] Sync agent state from VPS at 2026-05-19 12:16:58 --- AGENT_BOARD.md | 11 ++++++----- USER_STATUS.md | 31 ++++++++++++++++--------------- 2 files changed, 22 insertions(+), 20 deletions(-) diff --git a/AGENT_BOARD.md b/AGENT_BOARD.md index a989413..784622b 100644 --- a/AGENT_BOARD.md +++ b/AGENT_BOARD.md @@ -45,7 +45,7 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con | G0A Collaboration mechanism aligned | User-approved agent roles, Git polling MVP, sync-health handling, status entry, and hard safety boundaries | ORCHESTRATOR | Done | | G0B OpenClaw system requirements aligned | User-approved target architecture, component boundaries, PC permissions, Tailscale role, phone/QQ behavior, and G2/G3/G4 acceptance criteria | ORCHESTRATOR | Done | | G1 Baseline discovered | PC and VPS read-only status snapshots accepted by independent verifiers | PC_EXECUTOR, VPS_EXECUTOR, verifiers | Done | -| G2 Gateway/node pairing ready | PC `node run` evidence and VPS approval evidence | PC_EXECUTOR, VPS_EXECUTOR | Pending | +| G2 Gateway/node pairing ready | PC `node run` evidence and VPS approval evidence | PC_EXECUTOR, VPS_EXECUTOR | In Progress | | G3 Execution smoke test | Harmless command result proves execution came from the PC node | PC_VERIFIER | Pending | | G4 Persistent service verified | `node install/start/status` and reboot survival evidence | PC_VERIFIER, CORRECTION | Pending | | G5 Security posture reviewed | Secrets absent, public exposure avoided, least-privilege notes captured | VPS_VERIFIER, CORRECTION | Pending | @@ -64,11 +64,11 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con | T6 | Verify VPS baseline before any VPS change | VPS_VERIFIER | T4 | Accepted | | T7 | Monitor drift, sync-health failures, conflicts, unsafe changes, and missing evidence | CORRECTION | G0A | Claimed | | T8 | Solidify COACH role, session freeze, and knowledge capture | COACH | T2.1 | Done | -| T9 | G2 PC foreground node run | PC_EXECUTOR | User G2 authorization, T7 healthy | Draft | +| T9 | G2 PC foreground node run | PC_EXECUTOR | User G2 authorization, T7 healthy | Ready | | T10 | G2 VPS pairing approval | VPS_EXECUTOR | T9, explicit approval authorization | Draft | | T11 | Verify G2 PC evidence | PC_VERIFIER | T9 | Draft | | T12 | Verify G2 VPS evidence and freeze compliance | VPS_VERIFIER | T10 | Draft | -| T13 | Guard G2 sync, secret, and freeze risks | CORRECTION | User G2 authorization | Draft | +| T13 | Guard G2 sync, secret, and freeze risks | CORRECTION | User G2 authorization | Ready | ## Confirmed OpenClaw Target Design @@ -100,9 +100,10 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con ## G2 Authorization Boundary -- `docs/G2_RUNBOOK.md` and T9-T13 are planning artifacts only while G2 is pending. -- G2 requires explicit user authorization before token injection, `openclaw node run`, VPS pairing approval, or any executor action. +- User authorized G2 on 2026-05-19 for foreground PC node run and corresponding VPS pairing approval only. +- T9 may proceed under `docs/G2_RUNBOOK.md`; T10 must wait for T9 evidence with a non-secret request/node ID before any approval. - G2 must remain foreground-only for the PC node; service persistence belongs to G4. +- G2 still forbids service persistence, `openclaw node install/start`, Nginx/Docker/website changes, firewall/network changes, and recording any token or secret. - G2 must not change the frozen `smartmotor.cloud` homepage, homepage-linked content, static assets, Nginx routing, Docker bind mounts, container images, `/opt/services/docker-compose.openclaw.yml`, or any equivalent website-affecting compose/service entries. ## Operating Rules diff --git a/USER_STATUS.md b/USER_STATUS.md index 25e968e..6191261 100644 --- a/USER_STATUS.md +++ b/USER_STATUS.md @@ -4,9 +4,9 @@ ## Current Stage -Stage 1C: G2 authorization-ready, execution not authorized. +Stage 2A: G2 authorized, foreground node pairing only. -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. +The user has authorized G2 only for the foreground Windows PC node run and corresponding VPS pairing approval described in `docs/G2_RUNBOOK.md`. Service persistence, `openclaw node install/start`, Nginx/Docker/website changes, firewall/network changes, and recording any token or secret remain forbidden. ## Completed @@ -14,6 +14,7 @@ The collaboration mechanism, target architecture, component boundaries, safety g - 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 was authorized on 2026-05-19 for foreground PC node run and corresponding VPS pairing approval only. - 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. @@ -23,33 +24,33 @@ The collaboration mechanism, target architecture, component boundaries, safety g ## Current Blockers - No active sync blocker is recorded. -- Connection setup is intentionally paused because G2 has not been explicitly authorized. +- VPS pairing approval must wait until PC_EXECUTOR produces a non-secret pairing request ID or pending node ID from T9. ## 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. +- PC_EXECUTOR may perform T9 exactly as `docs/G2_RUNBOOK.md` allows: write rollback note, set the Gateway token only in the local shell/session without recording it, and run the PC node in foreground mode. +- VPS_EXECUTOR may perform T10 only after T9 provides a matching non-secret request/node ID; approval must be limited to the intended pairing. ## Forbidden Actions -- Do not start Gateway/node pairing or approval. -- Do not run PC node setup commands. +- 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 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 -Review `docs/G2_RUNBOOK.md`, then decide whether to explicitly authorize G2 execution. +PC_EXECUTOR should claim T9, write the rollback note, and run only the foreground PC node flow from `docs/G2_RUNBOOK.md` without recording any token or secret. ## 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. +No additional user decision is needed before T9 starts, as long as PC_EXECUTOR stays within the G2 runbook and the restrictions above. A new decision is required for any service persistence, firewall/network change, Nginx/Docker/website change, G3 smoke test, or action outside the runbook. ## Confirmed Target Design @@ -70,11 +71,11 @@ If authorized later, G2 will allow token injection, foreground PC node run, and ## 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`. +- Snapshot refreshed: 2026-05-19 12:16 UTC+8 from tracked control-plane files. +- PC sync heartbeat: clean at `2026-05-19T12:16:23+08:00`. +- VPS sync heartbeat: clean at `2026-05-19T12:16:28+0800`. - Sync error files: none observed. - G2 runbook: `docs/G2_RUNBOOK.md` complete. -- G2 authorization: not granted. +- G2 authorization: granted only for foreground PC node run and corresponding VPS pairing approval. - Public website freeze: still active. -- Mutation/setup phase: not started. +- Mutation/setup phase: limited G2 foreground pairing may start; service persistence and infrastructure changes remain forbidden.