From 9ad0008facac638643c4728a9576c08dfc2ba869 Mon Sep 17 00:00:00 2001 From: wangzhendong Date: Fri, 15 May 2026 16:25:24 +0800 Subject: [PATCH] Sync agent state from PC at 2026-05-15 16:25:24 --- AGENT_BOARD.md | 15 ++++++++++++++- handoff/ORCHESTRATOR.md | 16 +++++++++------- 2 files changed, 23 insertions(+), 8 deletions(-) diff --git a/AGENT_BOARD.md b/AGENT_BOARD.md index 18912be..96e4176 100644 --- a/AGENT_BOARD.md +++ b/AGENT_BOARD.md @@ -37,7 +37,8 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con | Gate | Required Evidence | Owner | Status | |---|---|---|---| -| G0 Requirements aligned | User-approved mission, roles, and acceptance criteria | ORCHESTRATOR | Done | +| 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 final system effect, component responsibilities, PC execution permissions, Tailscale role, phone Control UI path, later channels, and G2/G3/G4 acceptance criteria | ORCHESTRATOR | Pending | | 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 | | G3 Execution smoke test | Harmless command result proves execution came from the PC node | PC_VERIFIER | Pending | @@ -60,6 +61,18 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con ## Acceptance Criteria Draft +G0B is still pending. Before G2 can open, ORCHESTRATOR must discuss and freeze: + +- Final effect: how phone, PC, and VPS should collaborate through OpenClaw. +- Responsibility boundaries for the VPS Gateway, DeepSeek, and the Docker stack. +- Windows PC execution-node allowed capabilities and forbidden capabilities. +- Whether Tailscale is an optional enhancement or a required prerequisite. +- Phone Control UI access path and acceptance method. +- Whether QQ or later channels are included in the current stage or deferred. +- Concrete acceptance criteria for G2 Gateway/node pairing, G3 execution smoke test, and G4 persistent service verification. + +Existing draft outcomes: + - The PC can act as an OpenClaw execution node connected to the existing Gateway. - The Gateway continues to coexist with Nginx, Gitea, Confluence, and Postgres on the VPS. - The existing `smartmotor.cloud` website content remains unchanged during filing review, including homepage content and linked content reachable from the homepage. diff --git a/handoff/ORCHESTRATOR.md b/handoff/ORCHESTRATOR.md index c4f5195..8a74007 100644 --- a/handoff/ORCHESTRATOR.md +++ b/handoff/ORCHESTRATOR.md @@ -21,21 +21,23 @@ Bootstrap the shared Gitea-backed control plane, then coordinate read-only basel - VPS target path: `/home/ubuntu/openclaw-control-plane`. - Access mode: HTTPS. - Default branch: `main`. -- G0 is complete: the user confirmed mission, role boundaries, non-mutation rule, communication MVP, freeze policy, and acceptance criteria. +- G0A collaboration mechanism is complete: the user confirmed agent roles, Git polling MVP, sync-health handling, `USER_STATUS.md` as user entry, and non-mutation/freeze boundaries. +- G0B OpenClaw system requirements are pending: final system effect, component responsibilities, PC execution permissions, Tailscale role, phone Control UI path, later channels, and G2/G3/G4 acceptance criteria must be discussed and frozen with the user. - G1 baseline is complete: PC_VERIFIER accepted T5 and VPS_VERIFIER accepted T6. - Strict `smartmotor.cloud` website freeze is a hard requirement during filing review. - Communication MVP uses polling Git sync scripts in `sync/` and task files in `tasks/`. - Sync-health recovered; T7 is no longer blocked and remains claimed for ongoing CORRECTION monitoring. -- Mutation-stage work is still not authorized in this session. +- Mutation-stage work and G2 are not authorized while G0B is pending. - `USER_STATUS.md` is the user-facing status entry; internal agent ledgers should not be required reading for the user. - The polling sync is intentionally temporary; design an async notification/coordinator layer when PC/VPS baseline work is stable. ## Next Actions -1. Keep T7 active for CORRECTION monitoring of sync-health, drift, missing evidence, and freeze-policy risk. -2. Keep `USER_STATUS.md` current when gate, blocker, heartbeat, or required user decision changes. -3. Track the VPS verifier follow-up observations before any future mutation task: service path naming drift and Nginx route/config anomaly. -4. Do not open G2 or any mutation-stage task until explicitly authorized. +1. Complete G0B with the user before opening G2. +2. Keep T7 active for CORRECTION monitoring of sync-health, drift, missing evidence, and freeze-policy risk. +3. Keep `USER_STATUS.md` current when gate, blocker, heartbeat, or required user decision changes. +4. Track the VPS verifier follow-up observations before any future mutation task: service path naming drift and Nginx route/config anomaly. +5. Do not open G2 or any mutation-stage task until G0B is accepted and the user explicitly authorizes the next stage. ## Open Questions @@ -45,4 +47,4 @@ Bootstrap the shared Gitea-backed control plane, then coordinate read-only basel ## Last Update -Added `USER_STATUS.md` as the user-facing status entry. G0 and G1 are complete, sync-health is healthy, T7 remains claimed, and no PC/VPS configuration mutation or G2 work is authorized. +Corrected gate model: G0A is complete, G0B is pending, and G1 baseline remains complete. G2 and mutation-stage work remain unauthorized until OpenClaw system requirements and acceptance criteria are confirmed with the user.