Sync agent state from PC at 2026-05-15 11:32:06

AGENT_BOARD.md

@@ -35,7 +35,7 @@ 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 |
+| G0 Requirements aligned | User-approved mission, roles, boundaries, communication MVP, freeze rule, and acceptance criteria | ORCHESTRATOR | Done |
 | G1 Baseline discovered | PC and VPS read-only status snapshots | PC_EXECUTOR, VPS_EXECUTOR, verifiers | Pending |
 | 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 |

handoff/ORCHESTRATOR.md

@@ -21,24 +21,26 @@ 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.
 - 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/`.
 - The polling sync is intentionally temporary; design an async notification/coordinator layer when PC/VPS baseline work is stable.
+- Before verified G1 baseline completion, execution agents may perform only read-only discovery and evidence capture.
 
 ## Next Actions
 
-1. Commit and push the communication MVP files to Gitea.
+1. Keep `AGENT_BOARD.md` as the source of truth for the initial task run; do not switch to Gitea Issues yet.
-2. Ask the user to start or approve starting one sync script on PC and one on VPS.
+2. Assign T3 to PC_EXECUTOR for read-only PC baseline evidence.
-3. Run G0 requirements and acceptance review with the user.
+3. Assign T4 to VPS_EXECUTOR for read-only VPS baseline evidence.
-4. Assign PC and VPS read-only baseline tasks in their respective Cursor windows.
+4. Assign T5 to PC_VERIFIER and T6 to VPS_VERIFIER after executor evidence exists.
-5. Require verifier review before any mutation.
+5. Keep T7 available for CORRECTION to handle drift, conflicts, unsafe changes, or missing evidence.
+6. Require verifier acceptance of G1 before any PC/VPS configuration mutation.
 
 ## 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 the async notification/coordinator design start after baseline evidence is stable?
-- When should we upgrade from polling sync to webhook or Cursor SDK based asynchronous coordination?
 
 ## Last Update
 
-Control-plane repository scaffold prepared locally.
+G0 completed with user confirmation. Work split into read-only executor baseline tasks, independent verifier tasks, and a CORRECTION drift-monitoring task. No PC/VPS configuration mutation is authorized.

tasks/T3-PC-baseline.md

@@ -11,12 +11,14 @@ PC_EXECUTOR
 ## Dependencies
 
 - T2 sync scaffold available on PC and VPS
-- G0 requirement review may still be pending; this task is read-only only
+- G0 requirement review complete
 
 ## Scope
 
 Collect current Windows PC baseline evidence for OpenClaw execution-node readiness.
 
+This task is read-only only. It must not install services, edit firewall rules, change environment variables, expose ports, or alter local OpenClaw configuration.
+
 ## Allowed Actions
 
 - Read local state.

tasks/T4-VPS-baseline.md

@@ -11,12 +11,14 @@ VPS_EXECUTOR
 ## Dependencies
 
 - T2 sync scaffold available on PC and VPS
-- G0 requirement review may still be pending; this task is read-only only
+- G0 requirement review complete
 
 ## Scope
 
 Collect current VPS baseline evidence for OpenClaw Gateway, Gitea, Docker stack, and approval-command readiness.
 
+This task is read-only only. The `smartmotor.cloud` website freeze is a hard constraint: do not change homepage content, linked page content reachable from the homepage, static assets, Nginx routing, Docker bind mounts, container images, service state, or `/opt/services/docker-composite.yml` entries that could alter public website output.
+
 ## Allowed Actions
 
 - Read VPS service state.

tasks/T5-verify-baselines.md

@@ -1,36 +1,36 @@
-# T5 - Verify PC and VPS Baselines
+# T5 - Verify PC Baseline
 
 ## Status
 
-draft
+pending
 
 ## Owner
 
-PC_VERIFIER and VPS_VERIFIER
+PC_VERIFIER
 
 ## Dependencies
 
 - T3 done
-- T4 done
 
 ## Scope
 
-Independently verify PC and VPS baseline evidence before any configuration mutation.
+Independently verify PC baseline evidence before any PC configuration mutation.
 
 ## Required Evidence
 
-- PC baseline evidence reviewed and accepted or returned with findings
+- PC baseline evidence reviewed and accepted or returned with findings.
-- VPS baseline evidence reviewed and accepted or returned with findings
+- Confirmation that PC_EXECUTOR did not accept its own work.
+- Confirmation that no PC service, firewall, environment variable, scheduled task, OpenClaw config, or public port exposure was changed.
+- Confirmation that evidence contains no secrets.
 - Confirmation that no executor accepted its own work
-- Confirmation that frozen website policy remains intact
 
 ## Stop Conditions
 
 - Missing evidence.
 - Evidence includes secrets.
 - Evidence shows drift from the mission or from `OPENCLAW_EXEC_NODE_PLAN.md`.
-- Evidence suggests a required mutation before G0 has been completed.
+- Evidence suggests a required mutation before G1 has been accepted.
 
 ## Acceptance
 
-ORCHESTRATOR may move G1 to accepted only after both verifier roles record acceptance.
+ORCHESTRATOR may count the PC half of G1 as accepted only after PC_VERIFIER records acceptance.