# T7 - Correction Monitor

## Status

blocked

## Owner

CORRECTION

## Dependencies

- G0 complete

## Scope

Monitor the control-plane task flow for drift, sync-health failures, conflicts, unsafe changes, missing evidence, and rollback needs.

This task does not authorize PC or VPS configuration mutation. CORRECTION may block tasks and write findings to `handoff/CORRECTION.md`.

## Required Evidence

- Any detected sync conflict, unsafe task expansion, missing evidence, or freeze-policy risk recorded in `handoff/CORRECTION.md`.
- Any task blocked by CORRECTION includes the reason and the evidence gap or safety concern.
- Confirmation that no secrets were written into repo files, evidence, handoffs, commits, or chat.
- Fresh `sync-state/heartbeat-pc.json` and `sync-state/heartbeat-vps.json`, or a documented warning/blocker.
- Absence of `sync-state/error-pc.md` and `sync-state/error-vps.md`, or a documented blocker if either exists.

## Monitoring Findings

- 2026-05-15 11:42 UTC+8: Read `AGENT_BOARD.md`, `README.md`, `.cursor/rules/agent-orchestration.mdc`, this task, and all relevant PC/VPS handoffs and baseline tasks.
- Current state: T3/T4 are `ready`, T5/T6 are `draft`, and G1 remains pending.
- Evidence state: only `evidence/README.md` exists; no PC/VPS baseline or verifier evidence exists yet.
- No executor overreach, frozen `smartmotor.cloud` website mutation, pre-G1 configuration mutation, rollback-note gap, sync conflict, or secret-bearing evidence was detected in tracked repository contents.
- Correction decision: no task is blocked in this pass, but no PC/VPS mutation-stage work is authorized until G1 is independently verified and accepted.
- 2026-05-15 12:11 UTC+8: `git pull` reported the repo was already up to date, then CORRECTION reread the board, orchestration rule, T7, sync docs, and relevant executor baseline state.
- Sync-health is blocked: `sync-state/heartbeat-pc.json` and `sync-state/heartbeat-vps.json` are both missing, so heartbeat freshness cannot be established.
- No `sync-state/error-*.md` file is present in this pass.
- While sync-health is blocked, CORRECTION blocks cross-device dependent tasks and all mutation-stage work.
- T3 and T4 are now `done` with baseline evidence present at `evidence/pc-baseline-20260515.md` and `evidence/vps-baseline-20260515.md`; T5 and T6 remain `draft`, so G1 is not accepted.
- No executor self-acceptance, frozen website mutation, pre-G1 configuration mutation, or secret-bearing evidence was detected in this pass.
- Drift warning: `AGENT_BOARD.md` lists G0 as `Pending`, while task dependencies and T7 say G0 is complete. ORCHESTRATOR should reconcile the gate status.
- VPS baseline contains a verifier-facing route/config drift note; this requires VPS_VERIFIER review and does not authorize CORRECTION to modify VPS config.

## Current Block

- Reason: missing PC and VPS heartbeat files under `sync-state/`.
- Effect: block cross-device dependent tasks and all mutation-stage work until both heartbeat files exist and are fresh.
- Mutation-stage examples blocked: Gateway/node pairing, approval actions, service install/start, restarts, config edits, token rotation, public exposure changes, and deployment changes.

## Stop Conditions

- A task attempts PC/VPS configuration changes before G1 acceptance.
- Any evidence or handoff includes a secret.
- Any VPS task risks changing frozen `smartmotor.cloud` public website output.
- Sync scripts report conflict, authentication failure, or unexpected files.
- PC or VPS heartbeat is older than 5 minutes.
- Baseline evidence exists on one side but is not visible through the synchronized control-plane repository.

## Acceptance

ORCHESTRATOR reviews CORRECTION findings before allowing any mutation-stage task to proceed.