# CORRECTION Handoff

## Role

Detect drift, unsafe assumptions, missing evidence, sync-health failures, conflicting edits, and tasks that no longer align with the mission.

## Watchlist

- Agents editing outside their role scope.
- Executors marking their own work as accepted.
- Secrets appearing in repo files, handoffs, evidence, terminal captures, or commits.
- Any attempt to alter the frozen `smartmotor.cloud` website, homepage-linked content, static assets, Nginx routing, bind mounts, container images, `/opt/services/docker-compose.openclaw.yml`, or any equivalent compose/service entries that affect public website output.
- PC/VPS agents making simultaneous config changes before baseline verification.
- Gitea sync conflicts in `AGENT_BOARD.md` or handoff files.
- Stale or missing heartbeat files under `sync-state/`.
- Any `sync-state/error-*.md` file.
- PC/VPS evidence or task status visible on one side but not synchronized through Gitea.
- Changes to Nginx, Docker, or Windows services without rollback notes.

## Sync Health Policy

- Warning: peer heartbeat older than 2 minutes.
- Blocked: peer heartbeat older than 5 minutes.
- Blocked: any sync error file exists.
- Blocked: either side reports persistent Git `ahead`, `behind`, conflict, or dirty state that prevents evidence visibility.
- If sync is blocked, CORRECTION should block cross-device dependent tasks and prevent mutation-stage work until communication is healthy.

## Current State

- 2026-05-19 12:22 UTC+8: Audited role-misdirection event after `git pull` reported the repo was already up to date.
- Background under review: prompts intended for ORCHESTRATOR were mistakenly sent to VPS_VERIFIER during the recent hour.
- Recent git history shows VPS-origin commits modified files outside VPS_VERIFIER's allowed write scope:
  - `1400aea` modified `AGENT_BOARD.md` and `USER_STATUS.md`.
  - `588db23` modified `handoff/ORCHESTRATOR.md`, `tasks/T9-G2-PC-node-run.md`, `tasks/T10-G2-VPS-pairing-approve.md`, and `tasks/T13-G2-correction-guard.md`.
  - `5134f68` modified `handoff/CORRECTION.md`, `handoff/PC_EXECUTOR.md`, `handoff/VPS_EXECUTOR.md`, and `tasks/T7-correction-monitor.md`.
- These file changes align with ORCHESTRATOR/COACH/CORRECTION/executor handoff responsibilities, not VPS_VERIFIER responsibilities. Treat this as a role-scope incident requiring ORCHESTRATOR review and adoption or correction.
- `handoff/VPS_VERIFIER.md` now self-reports that VPS_VERIFIER modified only `evidence/verify-vps-baseline-20260515.md` and `handoff/VPS_VERIFIER.md`; that self-report is inconsistent with the VPS-origin commits above if those commits were produced by the misdirected VPS_VERIFIER session.
- No rollback was performed.
- No evidence was found that VPS_VERIFIER executed live G2 approval, `nodes pending`, `devices approve`, `nodes approve`, service restart/reload, token rotation, Gateway config mutation, Nginx/Docker/compose/bind-mount/image change, or frozen website content/routing changes during the misdirection window.
- Read-only VPS baseline verification evidence remains consistent with T6 scope: Docker/Gateway/Nginx/HTTPS/CLI `--help` checks only; no approval except `--help` checks.
- Evidence directory currently contains only baseline and baseline-verifier evidence; no `pc-g2-*`, `vps-g2-*`, or G2 approval evidence exists.
- `rollback/` contains no G2 rollback notes, so no G2 token/run/approval action should be treated as having begun.
- Secret scan of evidence found no likely secret values; current tracked text contains policy, negative, and placeholder references only.
- Sync-health is currently healthy by tracked files: both heartbeat files exist, are fresh for this audit window, and no `sync-state/error-*.md` files are present.
- Correction decision: block G2 progression until ORCHESTRATOR explicitly reviews the role-scope incident, reclaims ownership of ORCHESTRATOR-owned files and status changes, and restates the authorized next step.

## Next Actions

1. ORCHESTRATOR must review and either adopt or correct the VPS-origin changes to `AGENT_BOARD.md`, `USER_STATUS.md`, `handoff/ORCHESTRATOR.md`, T9/T10/T13, executor handoffs, and T7.
2. Keep T9/T10 and any mutation-stage action paused until ORCHESTRATOR restates the current gate/task state after the role-misdirection audit.
3. VPS_VERIFIER should remain limited to VPS verification evidence and `handoff/VPS_VERIFIER.md` unless explicitly reassigned.
4. Continue forbidding service persistence, `openclaw node install/start`, Nginx/Docker/website changes, firewall/network changes, public port exposure, and any token/secret recording.
5. If new `sync-state/error-*.md` files appear or heartbeat freshness exceeds policy thresholds, record a separate sync-health blocker.

## Last Update

2026-05-19 12:22 UTC+8 - Role-misdirection audit found cross-role file modifications from VPS-origin commits and requires ORCHESTRATOR takeover before G2 proceeds. No secret leak or VPS service/Nginx/Docker/website mutation was detected.

2026-05-19 12:16 UTC+8: G2 authorization guard update.

- User authorized G2 only for foreground PC node run and corresponding VPS pairing approval under `docs/G2_RUNBOOK.md`.
- T9 and T13 are ready; T10 remains draft until T9 produces a matching non-secret pairing request ID or pending node ID.
- Continue blocking service persistence, `openclaw node install/start`, Nginx/Docker/website changes, firewall/network changes, public port exposure, and any token/secret recording.
- Stop G2 if heartbeat becomes stale, any `sync-state/error-*.md` appears, evidence is not visible on both sides, request identity is ambiguous, or freeze compliance becomes uncertain.