152 lines
10 KiB
Markdown
152 lines
10 KiB
Markdown
# ORCHESTRATOR Handoff
|
|
|
|
## Role
|
|
|
|
Own requirements alignment, task decomposition, dependency tracking, and final acceptance.
|
|
|
|
## Current Objective
|
|
|
|
Coordinate freshly authorized G2 execution strictly under `docs/G2_RUNBOOK.md`: T13 guard and T9 foreground PC node run may proceed; T10 remains blocked until T9 evidence provides one matching non-secret request/node ID.
|
|
|
|
## Must Read
|
|
|
|
- `AGENT_BOARD.md`
|
|
- `OPENCLAW_EXEC_NODE_PLAN.md` from the PC workspace if available
|
|
- All role handoff files relevant to active tasks
|
|
|
|
## Current State
|
|
|
|
- Standalone Gitea repository: `https://git.smartmotor.cloud/wangzhendong/openclaw-control-plane.git`.
|
|
- PC local path: `D:\openclaw-control-plane`.
|
|
- VPS target path: `/home/ubuntu/openclaw-control-plane`.
|
|
- Access mode: HTTPS.
|
|
- Default branch: `main`.
|
|
- G0A collaboration mechanism is complete: the user confirmed agent roles, Git polling MVP, sync-health handling, `USER_STATUS.md` as user entry, and non-mutation/freeze boundaries.
|
|
- G0B OpenClaw system requirements are complete: QQ and phone Control UI are current-stage control entries, VPS Gateway is the always-on hub, DeepSeek may trigger white-listed actions, Windows PC is the main execution node, Tailscale is optional, and G2/G3/G4 acceptance criteria are frozen.
|
|
- G1 baseline is complete: PC and VPS baseline evidence were accepted by independent verifiers.
|
|
- 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.
|
|
- Fresh second G2 authorization was received and reconfirmed for ORCHESTRATOR in `D:\openclaw-control-plane` on 2026-05-19.
|
|
- `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 is In Progress under the limited runbook scope.
|
|
- The polling sync is intentionally temporary; design an async notification/coordinator layer when PC/VPS baseline work is stable.
|
|
- Filing-review freeze path wording has been corrected from the obsolete single `docker-composite.yml` reference to `/opt/services/docker-compose.openclaw.yml` plus any equivalent compose/service entries that could affect public website output.
|
|
|
|
## Next Actions
|
|
|
|
1. Keep `USER_STATUS.md` current when gate, blocker, heartbeat, or required user decision changes.
|
|
2. Keep T7/CORRECTION monitoring active for sync-health, drift, missing evidence, and freeze-policy risk.
|
|
3. Let CORRECTION claim T13 and verify sync/secret/freeze guardrails before or alongside T9.
|
|
4. Let PC_EXECUTOR claim T9, write `rollback/pc-g2-node-run-YYYYMMDD.md`, set token only in the local shell/session without recording it, and run only the foreground node command in `docs/G2_RUNBOOK.md`.
|
|
5. Keep T10 blocked until T9 evidence includes a matching non-secret pairing request ID or pending node ID.
|
|
6. Continue forbidding service persistence, `openclaw node install/start`, Nginx/Docker/website changes, firewall/network changes, G3 smoke test, G4 setup, and recording any token or secret.
|
|
|
|
## Open Questions
|
|
|
|
- When will T9 produce a matching non-secret pairing request ID or pending node ID for possible T10 approval?
|
|
- When should the Git polling MVP be upgraded to webhook, Issues, OpenClaw events, or Cursor SDK based coordination?
|
|
|
|
## Last Update
|
|
|
|
2026-05-19 12:27 UTC+8: ORCHESTRATOR took over after role-misdirection audit and paused G2 execution.
|
|
|
|
- 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:34 UTC+8: Generated `docs/G2_AUTHORIZATION_CARD.md`.
|
|
|
|
- Confirmed current target role is ORCHESTRATOR and workspace is `D:\openclaw-control-plane`.
|
|
- Confirmed G2 is paused/pending and old authorization must not be reused.
|
|
- Confirmed tracked sync-health is healthy: PC and VPS heartbeats are clean and no `sync-state/error-*.md` files were observed.
|
|
- No PC/VPS command was executed, no token was handled, no node was started, and no VPS approval was performed.
|
|
|
|
2026-05-19 12:37 UTC+8: Fresh second G2 authorization received in the correct target window/workspace.
|
|
|
|
- Target role/workspace confirmed: ORCHESTRATOR in `D:\openclaw-control-plane`.
|
|
- Sync-health confirmed healthy by tracked files: PC and VPS heartbeats are clean, and no `sync-state/error-*.md` files were observed.
|
|
- G2 moved to In Progress under the limited runbook scope.
|
|
- T13 and T9 are ready; T10 remains blocked until T9 evidence provides a matching non-secret request/node ID.
|
|
- ORCHESTRATOR did not execute PC/VPS commands, did not handle a token, did not start a node, and did not approve pairing.
|
|
|
|
2026-05-19 14:44 UTC+8: Fresh second G2 authorization was repeated in the correct target window/workspace.
|
|
|
|
- Target role/workspace confirmed again: ORCHESTRATOR in `D:\openclaw-control-plane`.
|
|
- Sync-health confirmed healthy again by tracked files: PC and VPS heartbeats are clean, and no `sync-state/error-*.md` files were observed.
|
|
- Existing state remains correct: G2 In Progress, T13/T9 Ready, T10 Blocked until T9 evidence provides a matching non-secret request/node ID.
|
|
- ORCHESTRATOR did not execute PC/VPS commands, did not handle a token, did not start a node, and did not approve pairing.
|
|
|
|
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 Pending, not in progress and 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.
|
|
|
|
2026-05-19 12:11 UTC+8: Completed G2 authorization-before-execution control-plane cleanup.
|
|
|
|
- `docs/G2_RUNBOOK.md` is complete as the G2 pre-execution runbook.
|
|
- `USER_STATUS.md` was refreshed with current sync-health snapshot and states that G2 is not authorized.
|
|
- `AGENT_BOARD.md` keeps G2 Pending and marks T2.1/T8 Done.
|
|
- Filing freeze references now use `/opt/services/docker-compose.openclaw.yml` and any equivalent website-affecting compose/service entries, instead of relying on the obsolete single `docker-composite.yml` path.
|
|
- No PC/VPS command was executed, no token was handled, no node was started, no VPS approval was performed, and no service was modified.
|
|
- Next step: wait for explicit user authorization before opening G2 execution tasks.
|
|
|
|
## Frozen G0B Summary
|
|
|
|
- QQ is included in the current stage as a primary natural-language entry.
|
|
- Phone Control UI must be able to start basic tasks, show status/results, and approve high-risk actions.
|
|
- VPS OpenClaw Gateway is the always-on hub for device connection, routing, approval flow, state aggregation, and audit.
|
|
- DeepSeek may understand, split, and autonomously trigger white-listed actions. High-risk or non-white-listed actions require human approval.
|
|
- Windows PC is the main execution node and may perform broad user-level local execution.
|
|
- PC system-level changes, service installation, network/firewall changes, and large destructive file operations require human approval and rollback notes.
|
|
- Tailscale is optional for administration, troubleshooting, and private-path enhancement. It is not a G2 prerequisite.
|
|
- G2/G3/G4 acceptance criteria are recorded in `AGENT_BOARD.md`.
|
|
|
|
## G2 Planning State
|
|
|
|
- T9: PC foreground node run, ready.
|
|
- T10: VPS pairing approval, blocked until T9 evidence.
|
|
- T11: PC G2 verification, draft.
|
|
- T12: VPS G2 verification and freeze compliance, draft.
|
|
- T13: G2 correction guard, ready.
|
|
- Authorization judgment: fresh second authorization is valid only for the G2 runbook scope and expires if sync blocks, role/workspace mismatches, secrets appear, pairing identity is ambiguous, steps drift from the runbook, or freeze risk appears.
|
|
|
|
## Session Freeze - 2026-05-19 14:46 UTC+8
|
|
|
|
Current phase: G2 limited foreground pairing is authorized under `docs/G2_RUNBOOK.md`.
|
|
|
|
Completed:
|
|
|
|
- G0A, G0B, and G1 accepted.
|
|
- Role-misdirection recovery completed and second G2 authorization reconfirmed.
|
|
- G2 control plane opened only for T13 and T9.
|
|
|
|
Blocked:
|
|
|
|
- T10 remains blocked until T9 evidence contains one matching non-secret pairing request/node ID.
|
|
- G3 smoke test and G4 persistence remain closed.
|
|
|
|
Safety constraints:
|
|
|
|
- Do not record secrets or `OPENCLAW_GATEWAY_TOKEN`.
|
|
- Do not run `openclaw node install/start`.
|
|
- Do not perform service persistence, service restart, Nginx/Docker/website/firewall/network changes, or public port exposure.
|
|
|
|
Next owner: PC_EXECUTOR for T9, with CORRECTION monitoring T13.
|
|
|
|
Single next action: PC_EXECUTOR claims T9, writes `rollback/pc-g2-node-run-YYYYMMDD.md`, then follows only the foreground node flow in `docs/G2_RUNBOOK.md`.
|
|
|
|
Resume prompt:
|
|
|
|
```text
|
|
You are ORCHESTRATOR resuming OpenClaw G2.
|
|
Read USER_STATUS.md, AGENT_BOARD.md, handoff/ORCHESTRATOR.md, tasks/T9-G2-PC-node-run.md, tasks/T10-G2-VPS-pairing-approve.md, tasks/T13-G2-correction-guard.md, docs/G2_RUNBOOK.md, and sync-state/README.md.
|
|
Current state: G2 is In Progress under limited runbook scope; T13 and T9 are Ready; T10 is Blocked until T9 produces one matching non-secret pairing request/node ID.
|
|
Do not execute PC/VPS commands from ORCHESTRATOR. Do not handle or record secrets. Keep G3/G4 closed.
|
|
```
|