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

This commit is contained in:
wangzhendong
2026-05-15 11:32:38 +08:00
parent d9909ea26f
commit 9e05c877f9
5 changed files with 84 additions and 3 deletions

View File

@@ -65,7 +65,7 @@ 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.
- 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.
- Before G0 and verified G1 baseline completion, executors may perform only read-only discovery and evidence capture.
- Before 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

View File

@@ -18,6 +18,14 @@ Tasks are the handoff contract between agents. They are not a real-time queue; s
- Verifiers update verification tasks and may mark executor tasks accepted after review.
- CORRECTION may mark a task blocked if it detects drift or unsafe execution.
## G0 Boundary
- G0 is complete only for requirements, role boundaries, and acceptance criteria.
- Until G1 baseline evidence is independently verified, executor tasks are read-only discovery tasks.
- No PC/VPS configuration mutation, service restart, network exposure change, approval action, or deployment change is authorized by a task unless ORCHESTRATOR explicitly opens a later gate.
- The `smartmotor.cloud` filing-review freeze is a hard constraint for all VPS tasks.
- Git polling sync plus task files are the MVP communication layer; future work should upgrade or supplement this with asynchronous notification or a coordinator after baseline work is stable.
## File Naming
Use:

View File

@@ -2,7 +2,7 @@
## Status
pending
draft
## Owner
@@ -22,7 +22,6 @@ Independently verify PC baseline evidence before any PC configuration mutation.
- 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
## Stop Conditions

View File

@@ -0,0 +1,38 @@
# T6 - Verify VPS Baseline
## Status
draft
## Owner
VPS_VERIFIER
## Dependencies
- T4 done
## Scope
Independently verify VPS baseline evidence before any VPS configuration mutation.
The `smartmotor.cloud` filing-review freeze is a hard constraint throughout verification.
## Required Evidence
- VPS baseline evidence reviewed and accepted or returned with findings.
- Confirmation that VPS_EXECUTOR did not accept its own work.
- Confirmation that no 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 were changed.
- Confirmation that Gateway, Nginx, Gitea, Confluence, and Postgres coexistence was only observed, not modified.
- Confirmation that evidence contains no secrets.
## Stop Conditions
- Missing evidence.
- Evidence includes secrets.
- Evidence shows drift from the mission or frozen website policy.
- Evidence suggests a required mutation before G1 has been accepted.
## Acceptance
ORCHESTRATOR may count the VPS half of G1 as accepted only after VPS_VERIFIER records acceptance.

View File

@@ -0,0 +1,36 @@
# T7 - Correction Monitor
## Status
ready
## Owner
CORRECTION
## Dependencies
- G0 complete
## Scope
Monitor the control-plane task flow for drift, conflicts, unsafe changes, missing evidence, and rollback needs.
This task does not authorize PC or VPS configuration mutation. CORRECTION may block tasks and write findings to `handoff/CORRECTION.md`.
## Required Evidence
- Any detected sync conflict, unsafe task expansion, missing evidence, or freeze-policy risk recorded in `handoff/CORRECTION.md`.
- Any task blocked by CORRECTION includes the reason and the evidence gap or safety concern.
- Confirmation that no secrets were written into repo files, evidence, handoffs, commits, or chat.
## Stop Conditions
- A task attempts PC/VPS configuration changes before G1 acceptance.
- Any evidence or handoff includes a secret.
- Any VPS task risks changing frozen `smartmotor.cloud` public website output.
- Sync scripts report conflict, authentication failure, or unexpected files.
## Acceptance
ORCHESTRATOR reviews CORRECTION findings before allowing any mutation-stage task to proceed.