# 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

- Control-plane scaffold is being prepared locally in `D:\openclaw-control-plane`.
- Remote Gitea repository has been created and cloned locally.

## Next Actions

1. Verify `sync-state/heartbeat-pc.json` and `sync-state/heartbeat-vps.json` are present and fresh after both sync scripts run.
2. Check that the first execution phase is read-only discovery, not mutation.
3. Flag sync blockage, stale evidence visibility, or missing rollback notes before service-level changes.

## Last Update

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.