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-19 12:28:19

Browse Source
This commit is contained in:
wangzhendong
2026-05-19 12:28:19 +08:00
parent 1ef07aef07
commit f64809990a
4 changed files with 41 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
handoff/ORCHESTRATOR.md
View File

@@ -6,7 +6,7 @@ Own requirements alignment, task decomposition, dependency tracking, and final a
## Current Objective
Coordinate authorized G2 execution strictly under `docs/G2_RUNBOOK.md`: foreground PC node run first, then corresponding VPS pairing approval only after a matching non-secret request/node ID exists.
Correct the control plane after a role-misdirection incident, keep G2 paused, and ensure no executor starts token injection, foreground node run, or VPS pairing approval without fresh explicit user authorization.
## Must Read
@@ -27,7 +27,7 @@ Coordinate authorized G2 execution strictly under `docs/G2_RUNBOOK.md`: foregrou
- 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 is authorized as of 2026-05-19, limited to foreground PC node run and corresponding VPS pairing approval under `docs/G2_RUNBOOK.md`.
- G2 execution is paused after the role-misdirection audit. Any earlier G2 authorization must be treated as not active until the user gives fresh explicit authorization after ORCHESTRATOR correction.
- `docs/G2_RUNBOOK.md` has been prepared as the G2 execution-before-action runbook. It does not authorize execution by itself.
- Sync-health is currently healthy: tracked PC and VPS heartbeats are present and clean, and no `sync-state/error-*.md` files are observed in the latest control-plane snapshot.
- T2.1 and T8 are now treated as complete control-plane setup work; G2 remains Pending.
@@ -36,24 +36,31 @@ Coordinate authorized G2 execution strictly under `docs/G2_RUNBOOK.md`: foregrou
## Next Actions
1. Let PC_EXECUTOR claim T9, write `rollback/pc-g2-node-run-YYYYMMDD.md`, set the Gateway token only in the local shell/session without recording it, and run only the foreground PC node command from `docs/G2_RUNBOOK.md`.
1. Keep T9/T10/T13 blocked and do not allow token injection, foreground node run, or VPS pairing approval.
2. Keep `USER_STATUS.md` current when gate, blocker, heartbeat, or required user decision changes.
3. Keep T7/CORRECTION monitoring active for sync-health, drift, missing evidence, and freeze-policy risk.
4. Keep T10 draft until T9 evidence includes a matching non-secret pairing request ID or pending node ID.
5. When T10 becomes eligible, require `rollback/vps-g2-approve-YYYYMMDD.md` before approval and approve only the matching request/node.
6. Continue forbidding service persistence, `openclaw node install/start`, Nginx/Docker/website changes, firewall/network changes, and recording any token or secret.
4. If the user later gives fresh explicit G2 authorization, move T13 then T9 to ready, keep T10 blocked until T9 evidence includes a matching non-secret pairing request ID or pending node ID, and require rollback notes before any token/run/approval action.
5. Continue forbidding service persistence, `openclaw node install/start`, Nginx/Docker/website changes, firewall/network changes, and recording any token or secret.
## Open Questions
- When should the user authorize G2 Gateway/node pairing?
- When should the user give fresh explicit authorization for G2 Gateway/node pairing after this correction?
- When should the Git polling MVP be upgraded to webhook, Issues, OpenClaw events, or Cursor SDK based coordination?
## Last Update
2026-05-19 12:16 UTC+8: User authorized G2 with strict scope.
2026-05-19 12:27 UTC+8: ORCHESTRATOR took over after role-misdirection audit and paused G2 execution.
- Allowed scope: foreground PC node run and corresponding VPS pairing approval under `docs/G2_RUNBOOK.md`.
- T9 and T13 are ready; T10 remains draft until T9 provides a matching non-secret request/node ID.
- VPS_VERIFIER self-reported that prompts intended for ORCHESTRATOR were mistakenly sent to VPS_VERIFIER.
- CORRECTION found cross-role control-plane edits from VPS-origin commits but no evidence of live G2 approval, token handling, service restart/reload, Gateway config mutation, Nginx/Docker/website mutation, or secret leak.
- ORCHESTRATOR adopts `docs/G2_RUNBOOK.md` as planning material only, but corrects the active state: G2 is Pending, T9/T10/T13 are blocked, and fresh explicit user authorization is required before any G2 execution.
- No PC/VPS command was executed by ORCHESTRATOR during this correction.
2026-05-19 12:16 UTC+8: Prior G2 authorization record is superseded by the 12:27 role-misdirection correction.
- Previously recorded allowed scope: foreground PC node run and corresponding VPS pairing approval under `docs/G2_RUNBOOK.md`.
- Current corrected state: this authorization is paused and must not be used for execution without fresh explicit user confirmation.
- T9/T10/T13 are blocked.
- G2 quality gate is In Progress, not accepted.
- No PC/VPS command was executed by ORCHESTRATOR, no token was handled, no node was started here, no VPS approval was performed here, and no service was modified.