openclaw-control-plane/tasks/T7-correction-monitor.md

T7 - Correction Monitor

Status

claimed

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-19 12:27 UTC+8: ORCHESTRATOR took over the role-misdirection incident and corrected active control-plane state. No G2 execution evidence, G2 rollback notes, token handling, node run, VPS approval, service/Nginx/Docker/website mutation, or secret leak was found. G2 is now paused: T9/T10/T13 are blocked, G2 quality gate is Pending, and fresh explicit user authorization is required before any G2 execution can proceed.
• 2026-05-19 12:37 UTC+8: ORCHESTRATOR received the fresh second G2 authorization in the correct target window/workspace. Sync-health is healthy by tracked files, no sync-state/error-*.md files are present, and role/workspace matched. G2 may proceed only within docs/G2_RUNBOOK.md: T13 and T9 are ready; T10 remains blocked until T9 produces a matching non-secret request/node ID.
• 2026-05-19 12:22 UTC+8: Audited role-misdirection event after git pull reported the repo was already up to date. User reported that prompts intended for ORCHESTRATOR were mistakenly sent to VPS_VERIFIER.
• Role-scope incident: VPS-origin commits in the recent audit window modified files outside VPS_VERIFIER's write scope. 1400aea changed AGENT_BOARD.md and USER_STATUS.md; 588db23 changed handoff/ORCHESTRATOR.md, T9, T10, and T13; 5134f68 changed handoff/CORRECTION.md, handoff/PC_EXECUTOR.md, handoff/VPS_EXECUTOR.md, and T7.
• If those commits came from the misdirected VPS_VERIFIER session, they are越权 control-plane edits. Even if the content is directionally reasonable, ORCHESTRATOR must review and explicitly adopt or correct it.
• handoff/VPS_VERIFIER.md self-reports only evidence/verify-vps-baseline-20260515.md and handoff/VPS_VERIFIER.md as files modified by VPS_VERIFIER. This is inconsistent with the VPS-origin cross-role commits if they were produced by the same misdirected role session.
• No evidence was found of live VPS 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 output change during this audit.
• Evidence contains only baseline and baseline-verifier files; no G2 PC node-run evidence, VPS approval evidence, or G2 rollback notes exist.
• Secret scan of evidence found no likely secret values. Current tracked references are policy/negative/placeholders, not exposed credentials.
• Sync-health is not blocked in this audit: both heartbeat files exist and no sync-state/error-*.md files are present.
• Correction decision: block G2 progression and mutation-stage work until ORCHESTRATOR takes over, reconciles the cross-role edits, and restates the authorized next step.
• 2026-05-19 12:16 UTC+8: User authorized G2 with strict scope: foreground PC node run and corresponding VPS pairing approval only. T9/T13 are ready; T10 waits for T9 evidence with a matching non-secret request/node ID. Continue blocking service persistence, openclaw node install/start, Nginx/Docker/website changes, firewall/network changes, and any token/secret recording.
• 2026-05-19 12:07 UTC+8: User confirmed sync-health is healthy and T7 sync-health blocked state is cleared. G2 entered pre-execution planning only. docs/G2_RUNBOOK.md and G2 task files define authorization gates, stop conditions, rollback, secret handling, and filing-freeze constraints. No G2 execution is authorized by this planning pass.
• 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.
• Historical note from 2026-05-15: T3/T4 were ready, T5/T6 were draft, and G1 was pending at that time.
• Historical planning state from 2026-05-19 12:07: G1 was done, T9/T10/T11/T12 remained draft, and G2 execution was not authorized at that time.
• 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: Fresh second authorization allows only T13 guard monitoring and T9 foreground PC node flow under docs/G2_RUNBOOK.md. Continue blocking T10 until a matching non-secret request/node ID exists, and block all service persistence, infrastructure changes, G3/G4 actions, and secret recording.

Current Block

• Reason: role-misdirection incident has been corrected and fresh second authorization has been recorded, but G2 remains narrowly scoped.
• Effect: allow T13 and T9 only under docs/G2_RUNBOOK.md; block T10 until T9 evidence identifies one matching non-secret pairing request/node ID; block G3/G4 and infrastructure mutation.
• Non-blocking findings: no secret leak, no sync-health blocker, and no evidence of VPS approve/service/Nginx/Docker/website mutation was found.

Stop Conditions

• A task attempts PC/VPS execution or configuration changes before explicit G2 authorization.
• 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.