T7 - Correction Monitor

Status

claimed

CORRECTION

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.

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.

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.

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.

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