51 lines
3.0 KiB
Markdown
51 lines
3.0 KiB
Markdown
# 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: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.
|
|
- Current G2 planning state from 2026-05-19: G1 is done, T9/T10/T11/T12 remain `draft`, and G2 execution is not authorized.
|
|
- 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: G2 execution is open only within the strict runbook scope. Block anything outside foreground PC node run, matching VPS pairing approval, non-secret evidence, and required rollback notes.
|
|
|
|
## 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.
|