wangzhendong/openclaw-control-plane
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Sync agent state from PC at 2026-05-21 16:44:08

Browse Source
This commit is contained in:
wangzhendong
2026-05-21 16:44:08 +08:00
parent 3541f43f5e
commit d63a56e9dd
2 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
handoff/CORRECTION.md
View File

@@ -86,9 +86,9 @@ Detect drift, unsafe assumptions, missing evidence, sync-health failures, confli
1. Continue monitoring T13 for sync-health, secret, role/workspace, pairing-identity, and freeze-policy stop conditions.
2. T9 is ready under the current board state; CORRECTION should re-block only if sync-health fails, an error file appears, G2 authorization changes, or another guard stop condition appears.
3. Keep T10 blocked until T9 evidence includes one matching non-secret pairing request ID or pending node ID.
5. VPS_VERIFIER should remain limited to VPS verification evidence and `handoff/VPS_VERIFIER.md` unless explicitly reassigned.
6. Continue forbidding service persistence, `openclaw node install/start`, Nginx/Docker/website changes, firewall/network changes, public port exposure, G3/G4 actions, and any token/secret recording.
7. If new `sync-state/error-*.md` files appear or heartbeat freshness exceeds policy thresholds, record a separate sync-health blocker.
4. VPS_VERIFIER should remain limited to VPS verification evidence and `handoff/VPS_VERIFIER.md` unless explicitly reassigned.
5. Continue forbidding service persistence, `openclaw node install/start`, Nginx/Docker/website changes, firewall/network changes, public port exposure, G3/G4 actions, and any token/secret recording.
6. If new `sync-state/error-*.md` files appear or heartbeat freshness exceeds policy thresholds, record a separate sync-health blocker.
## Last Update