Sync agent state from PC at 2026-05-15 11:31:35
This commit is contained in:
@@ -50,11 +50,13 @@ 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 |
|
| 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 | 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 |
|
| 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 |
|
| T3 | Run read-only PC baseline discovery | PC_EXECUTOR | G0, T2.1 | Ready |
|
||||||
| T4 | Run read-only VPS baseline discovery | VPS_EXECUTOR | T2.1 | Ready |
|
| T4 | Run read-only VPS baseline discovery | VPS_EXECUTOR | G0, T2.1 | Ready |
|
||||||
| T5 | Verify both baselines before any config change | PC_VERIFIER + VPS_VERIFIER | T3, T4 | Pending |
|
| T5 | Verify PC baseline before any PC change | PC_VERIFIER | T3 | Pending |
|
||||||
|
| T6 | Verify VPS baseline before any VPS change | VPS_VERIFIER | T4 | Pending |
|
||||||
|
| T7 | Monitor drift, conflicts, unsafe changes, and missing evidence | CORRECTION | G0 | Ready |
|
||||||
|
|
||||||
## Acceptance Criteria Draft
|
## Acceptance Criteria
|
||||||
|
|
||||||
- The PC can act as an OpenClaw execution node connected to the existing Gateway.
|
- 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 Gateway continues to coexist with Nginx, Gitea, Confluence, and Postgres on the VPS.
|
||||||
@@ -63,6 +65,8 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con
|
|||||||
- Tailscale is optional for the OpenClaw public Gateway path, but available for safer device-to-device operations.
|
- 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.
|
- 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.
|
- Later QQ or other channels are added only after the Gateway/node path is verified.
|
||||||
|
- Before G0 and verified G1 baseline completion, executors may perform only read-only discovery and evidence capture.
|
||||||
|
- The current communication layer is the Git polling MVP under `sync/` plus task files under `tasks/`; after the baseline path is stable, it must be upgraded or supplemented with asynchronous notification or a coordinator.
|
||||||
|
|
||||||
## Operating Rules
|
## Operating Rules
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user