From 7cd1b08e289891b8a077bc191bafc6836dbbd877 Mon Sep 17 00:00:00 2001 From: wangzhendong Date: Tue, 19 May 2026 12:03:55 +0800 Subject: [PATCH] Sync agent state from PC at 2026-05-19 12:03:55 --- AGENT_BOARD.md | 40 ++++++++++++++++++++++++++++-------- USER_STATUS.md | 39 ++++++++++++++++++++++------------- handoff/ORCHESTRATOR.md | 35 ++++++++++++++++++++++--------- sync-state/heartbeat-pc.json | 6 +++--- 4 files changed, 85 insertions(+), 35 deletions(-) diff --git a/AGENT_BOARD.md b/AGENT_BOARD.md index c7468fa..a2e81b8 100644 --- a/AGENT_BOARD.md +++ b/AGENT_BOARD.md @@ -19,7 +19,10 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con - Frozen website policy: strict freeze during ICP/public-security filing review. Agents must not change the `smartmotor.cloud` homepage, content reachable from homepage links, static assets, Nginx routing, bind mounts, container images, or `/opt/services/docker-composite.yml` entries that could alter public website output. - Communication MVP: use Git-backed polling sync scripts under `sync/` plus task files under `tasks/`. This reduces manual pull/push but is not the final async-notification design. - Sync-health monitoring: CORRECTION monitors tracked heartbeat and error files under `sync-state/`; no separate sync monitor agent is used at this stage. +- User-facing status entry: `USER_STATUS.md`. Users should not need to read internal task, handoff, evidence, or sync-state files for routine status. - COACH role: the main user-facing chat acts as COACH by default, guiding workflow usability, session freeze, and knowledge capture without replacing ORCHESTRATOR. +- Confirmed OpenClaw target: QQ and phone Control UI are current-stage control entries; the VPS Gateway is the always-on hub; DeepSeek may trigger white-listed actions; Windows PC is the main execution node. +- Tailscale role: optional administration, troubleshooting, and private-path enhancement. It is not a G2 prerequisite; the main path uses the VPS Gateway. - Future communication target: when the baseline path is stable, design an event-driven coordinator using Gitea webhooks, Gitea Issues, OpenClaw events, or Cursor SDK agent orchestration. ## Agent Roles @@ -38,8 +41,9 @@ 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 | Pending | -| G1 Baseline discovered | PC and VPS read-only status snapshots | PC_EXECUTOR, VPS_EXECUTOR, verifiers | Pending | +| 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 | | 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 | @@ -53,20 +57,40 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con | T1 | Create standalone Gitea repo for this control plane | User + ORCHESTRATOR | T0 | Done | | T2 | Sync this scaffold to Gitea and open on PC/VPS Cursor | ORCHESTRATOR + VPS_EXECUTOR | T1 | Done | | T2.1 | Add polling sync and task-file communication MVP | ORCHESTRATOR | T2 | In Progress | -| T3 | Run read-only PC baseline discovery | PC_EXECUTOR | T2.1 | Ready | -| T4 | Run read-only VPS baseline discovery | VPS_EXECUTOR | T2.1 | Ready | -| T5 | Verify both baselines before any config change | PC_VERIFIER + VPS_VERIFIER | T3, T4 | Pending | +| T3 | Run read-only PC baseline discovery | PC_EXECUTOR | T2.1 | Accepted | +| T4 | Run read-only VPS baseline discovery | VPS_EXECUTOR | T2.1 | Accepted | +| T5 | Verify PC baseline before any PC change | PC_VERIFIER | T3 | Accepted | +| 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 | In Progress | -## Acceptance Criteria Draft +## Confirmed OpenClaw Target Design + +- QQ is included in the current stage as a primary natural-language entry. +- Phone Control UI must be able to start basic tasks, show status/results, and approve high-risk actions. +- VPS OpenClaw Gateway is the always-on hub for device connection, routing, approval flow, state aggregation, and audit. +- DeepSeek may understand, split, and autonomously trigger white-listed actions. High-risk or non-white-listed actions require human approval. +- Docker stack hosts Gateway alongside existing Gitea, Nginx, Confluence, and Postgres services. The `smartmotor.cloud` filing-review freeze remains a hard boundary. +- Windows PC is the main execution node and may perform broad user-level local execution. +- PC system-level changes, service installation, network/firewall changes, and large destructive file operations require human approval and rollback notes. +- Tailscale is optional for administration, troubleshooting, and private-path enhancement. It is not a G2 prerequisite. +- Future multiple PCs, phones, and endpoint model nodes should join through the same Gateway model. + +## Acceptance Criteria - 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. - No PC service port is exposed directly to the public internet. - Tailscale is optional for the OpenClaw public Gateway path, but available for safer device-to-device operations. -- Phone can be used as a control client after the execution path is stable. -- Later QQ or other channels are added only after the Gateway/node path is verified. +- Phone can be used as a control client for basic tasks, status/results, and high-risk approvals. +- QQ is included in the current stage as a natural-language control entry. + +## Gate Acceptance Details + +- G2 Gateway/node pairing is accepted only when the PC node can connect to the VPS Gateway, the VPS can show pending/approved node state, approval does not leak secrets, and the frozen `smartmotor.cloud` website output remains unchanged. +- G3 execution smoke test is accepted only when a harmless task starts from QQ or phone Control UI, routes through the Gateway to the Windows PC, returns visible results, and verifier evidence proves execution came from the PC rather than the VPS. +- G4 persistent service verification is accepted only when the PC node can run as a persistent service or startup item, service install/start/status and reboot survival evidence exist, rollback notes exist for system-level changes, and approval guardrails still work. ## Operating Rules diff --git a/USER_STATUS.md b/USER_STATUS.md index 6e1ec68..9cbb5ef 100644 --- a/USER_STATUS.md +++ b/USER_STATUS.md @@ -4,13 +4,14 @@ ## Current Stage -Stage 1B: Confirm the OpenClaw target design. +Stage 1B: OpenClaw target design confirmed. -The collaboration mechanism is ready, and PC/VPS baseline checks have both been independently accepted. The overall OpenClaw system requirements are not frozen yet, so the system must not enter connection/setup work. +The collaboration mechanism, target architecture, component boundaries, safety guardrails, and G2/G3/G4 acceptance criteria are now frozen. The system still must not enter connection/setup work until the user explicitly authorizes the next stage. ## Completed - Collaboration mechanism was confirmed: agent roles, Git polling MVP, sync-health monitoring, and this user-facing status page. +- 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. - 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. @@ -20,15 +21,14 @@ The collaboration mechanism is ready, and PC/VPS baseline checks have both been ## Current Blockers - No active sync blocker is recorded. -- OpenClaw system requirements and target effect are not confirmed yet. -- Connection setup is intentionally paused until the system target and acceptance criteria are frozen. +- Connection setup is intentionally paused because G2 has not been explicitly authorized. ## 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 discuss and document the OpenClaw target design with the user. +- ORCHESTRATOR may prepare G2 task split and rollback/evidence requirements if the user asks. ## Forbidden Actions @@ -41,19 +41,30 @@ The collaboration mechanism is ready, and PC/VPS baseline checks have both been ## Single Recommended Next Step -Confirm the OpenClaw target design before any connection/setup work. +Wait for explicit user authorization before opening G2 connection setup. ## User Decision Needed -The user needs to confirm these items: +Not needed immediately. -- Final effect: how phone, PC, and VPS should collaborate through OpenClaw. -- Responsibility boundaries for the VPS Gateway, DeepSeek, and the Docker stack. -- What the Windows PC execution node is allowed to do, and what it must never do. -- Whether Tailscale is optional enhancement or required before setup. -- Phone Control UI access path and acceptance method. -- Whether QQ or other later channels are included now or deferred. -- Concrete acceptance criteria for connection setup, smoke test, and persistent service verification. +The next decision, when ready, is whether to authorize G2: connect the Windows PC execution node to the VPS OpenClaw Gateway and prepare the QQ/phone control path. That authorization has not been granted yet. + +## Confirmed Target Design + +- QQ is included in the current stage as a primary natural-language entry. +- Phone Control UI must be able to start basic tasks, show status/results, and approve high-risk actions. +- VPS OpenClaw Gateway is the always-on hub for device connection, routing, approval flow, state aggregation, and audit. +- DeepSeek may understand, split, and autonomously trigger white-listed actions. High-risk or non-white-listed actions require human approval. +- Windows PC is the main execution node and may perform broad user-level local execution. +- PC system-level changes, service installation, network/firewall changes, and large destructive file operations require human approval and rollback notes. +- Tailscale is optional for administration, troubleshooting, or private-path enhancement. It is not a G2 prerequisite; the main path uses the VPS Gateway. +- Future multiple PCs, phones, and endpoint model nodes should join through the same Gateway model. + +## Frozen Acceptance Criteria + +- G2 connection setup is accepted only when the PC node can connect to the VPS Gateway, the VPS can show pending/approved node state, approval does not leak secrets, and the frozen `smartmotor.cloud` website output remains unchanged. +- G3 smoke test is accepted only when a harmless task starts from QQ or phone Control UI, routes through the Gateway to the Windows PC, returns visible results, and verifier evidence proves execution came from the PC rather than the VPS. +- G4 persistence is accepted only when the PC node can run as a persistent service or startup item, service install/start/status and reboot survival evidence exist, rollback notes exist for system-level changes, and approval guardrails still work. ## Latest Health Snapshot diff --git a/handoff/ORCHESTRATOR.md b/handoff/ORCHESTRATOR.md index 109052d..71aa2ef 100644 --- a/handoff/ORCHESTRATOR.md +++ b/handoff/ORCHESTRATOR.md @@ -6,7 +6,7 @@ Own requirements alignment, task decomposition, dependency tracking, and final a ## Current Objective -Bootstrap the shared Gitea-backed control plane, then coordinate read-only baseline discovery on PC and VPS. +Maintain the shared Gitea-backed control plane, keep user-facing status current, and coordinate the next gate only after explicit user authorization. ## Must Read @@ -21,24 +21,39 @@ 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`. +- 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 complete: QQ and phone Control UI are current-stage control entries, VPS Gateway is the always-on hub, DeepSeek may trigger white-listed actions, Windows PC is the main execution node, Tailscale is optional, and G2/G3/G4 acceptance criteria are frozen. +- G1 baseline is complete: PC and VPS baseline evidence were accepted by independent verifiers. - 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/`. +- `USER_STATUS.md` is the user-facing status entry; internal agent ledgers should not be required reading for the user. +- G2 and mutation-stage work are not authorized until the user explicitly opens the next stage. - The polling sync is intentionally temporary; design an async notification/coordinator layer when PC/VPS baseline work is stable. ## Next Actions -1. Commit and push the communication MVP files to Gitea. -2. Ask the user to start or approve starting one sync script on PC and one on VPS. -3. Run G0 requirements and acceptance review with the user. -4. Assign PC and VPS read-only baseline tasks in their respective Cursor windows. -5. Require verifier review before any mutation. +1. Keep `USER_STATUS.md` current when gate, blocker, heartbeat, or required user decision changes. +2. Keep T7/CORRECTION monitoring active for sync-health, drift, missing evidence, and freeze-policy risk. +3. If the user authorizes G2 later, split G2 into executor/verifier tasks with rollback notes and evidence requirements before any mutation. +4. Track VPS verifier follow-up observations before future mutation: service path naming drift and Nginx route/config anomaly. +5. Do not open G2 or perform Gateway/node pairing until explicitly authorized. ## Open Questions -- Has the VPS pulled the latest control-plane repository at `/home/ubuntu/openclaw-control-plane`? -- Should Gitea Issues be used immediately for task tracking, or should `AGENT_BOARD.md` remain the first source of truth for the initial run? -- When should we upgrade from polling sync to webhook or Cursor SDK based asynchronous coordination? +- When should the user authorize G2 Gateway/node pairing? +- When should the Git polling MVP be upgraded to webhook, Issues, OpenClaw events, or Cursor SDK based coordination? ## Last Update -Control-plane repository scaffold prepared locally. +G0B target design was frozen into `USER_STATUS.md` and `AGENT_BOARD.md`. No PC/VPS configuration mutation was performed, and G2 remains closed until explicit user authorization. + +## Frozen G0B Summary + +- QQ is included in the current stage as a primary natural-language entry. +- Phone Control UI must be able to start basic tasks, show status/results, and approve high-risk actions. +- VPS OpenClaw Gateway is the always-on hub for device connection, routing, approval flow, state aggregation, and audit. +- DeepSeek may understand, split, and autonomously trigger white-listed actions. High-risk or non-white-listed actions require human approval. +- Windows PC is the main execution node and may perform broad user-level local execution. +- PC system-level changes, service installation, network/firewall changes, and large destructive file operations require human approval and rollback notes. +- Tailscale is optional for administration, troubleshooting, and private-path enhancement. It is not a G2 prerequisite. +- G2/G3/G4 acceptance criteria are recorded in `AGENT_BOARD.md`. diff --git a/sync-state/heartbeat-pc.json b/sync-state/heartbeat-pc.json index 9fb1707..17e63e0 100644 --- a/sync-state/heartbeat-pc.json +++ b/sync-state/heartbeat-pc.json @@ -1,9 +1,9 @@ { "host": "pc", - "time": "2026-05-18T10:49:32+08:00", + "time": "2026-05-19T12:03:54+08:00", "branch": "main", - "head": "85086ed", - "status": "clean", + "head": "2289f6c", + "status": "dirty", "intervalSeconds": 30, "heartbeatEverySeconds": 60 }