96 lines
6.1 KiB
Markdown
96 lines
6.1 KiB
Markdown
# T13 - G2 Correction Guard
|
|
|
|
## Status
|
|
|
|
ready
|
|
|
|
## Owner
|
|
|
|
CORRECTION
|
|
|
|
## Dependencies
|
|
|
|
- Fresh G2 user authorization recorded by ORCHESTRATOR after role-misdirection correction
|
|
|
|
## Scope
|
|
|
|
Guard G2 execution against sync-health failures, missing evidence, unsafe task expansion, secret leakage, and frozen website policy risk.
|
|
|
|
This task does not authorize PC/VPS configuration mutation.
|
|
|
|
## Required Evidence
|
|
|
|
- Confirm `sync-state/heartbeat-pc.json` and `sync-state/heartbeat-vps.json` are present and fresh before G2 execution starts.
|
|
- Confirm no `sync-state/error-pc.md` or `sync-state/error-vps.md` file exists.
|
|
- Confirm fresh user authorization is limited to foreground PC node run and corresponding VPS pairing approval.
|
|
- Confirm PC and VPS agents can see the same latest G2 task state and evidence through Git.
|
|
- Block G2 if any task bypasses explicit user authorization, records a secret, or risks changing frozen `smartmotor.cloud` website output.
|
|
- Record findings in `handoff/CORRECTION.md` and, if needed, update this task status to `blocked`.
|
|
|
|
## Current Authorization
|
|
|
|
- Fresh second G2 authorization was recorded by ORCHESTRATOR on 2026-05-19 for target window ORCHESTRATOR in `D:\openclaw-control-plane`.
|
|
- Current state: ready for CORRECTION guard monitoring during G2.
|
|
- Allowed scope: foreground PC node run under `docs/G2_RUNBOOK.md` and corresponding VPS pairing approval after T9 produces a matching non-secret request/node ID.
|
|
- Forbidden: service persistence, `openclaw node install/start`, Nginx/Docker/website changes, firewall/network changes, and recording any token or secret.
|
|
|
|
## Pre-Flight Findings
|
|
|
|
- 2026-05-21 16:42 UTC+8: CORRECTION ran a fresh T13 guard check after `git pull` reported already up to date.
|
|
- Role/workspace confirmed: CORRECTION in `D:\openclaw-control-plane`.
|
|
- PC heartbeat confirmed present, fresh, and `clean`: `2026-05-21T16:42:02+08:00`.
|
|
- VPS heartbeat confirmed present, fresh, and `clean`: `2026-05-21T16:42:25+0800`.
|
|
- Sync error check: no `sync-state/error-*.md` files present.
|
|
- G2 status confirmed: still user-authorized and `In Progress`.
|
|
- T9 status confirmed: `ready`.
|
|
- T10 status confirmed: `blocked`.
|
|
- Decision: fresh guard PASS for the requested sync/G2/T9/T10 checks. CORRECTION did not execute PC/VPS commands, handle tokens, start node, or approve anything.
|
|
- 2026-05-19 16:29 UTC+8: CORRECTION ran a fresh T13 G2 correction guard check after `git pull` reported already up to date.
|
|
- Role/workspace confirmed: CORRECTION in `D:\openclaw-control-plane`.
|
|
- G2 status confirmed: still user-authorized and `In Progress`.
|
|
- T13 status confirmed: `ready`.
|
|
- T9 status confirmed: `blocked`; it must remain blocked until ORCHESTRATOR reviews this fresh PASS and explicitly releases T9.
|
|
- T10 status confirmed: `blocked` until T9 produces one matching non-secret pairing request ID or pending node ID.
|
|
- PC heartbeat confirmed present, fresh, and `clean`: `2026-05-19T16:28:36+08:00`.
|
|
- VPS heartbeat confirmed present, fresh, and `clean`: `2026-05-19T16:29:05+0800`.
|
|
- Sync error check: no `sync-state/error-*.md` files present.
|
|
- Evidence check: no current G2 node-run or VPS approval evidence exists; prior `evidence/pc-g2-node-run-20260519.md` was deleted by a later PC sync commit.
|
|
- Rollback check: `rollback/pc-g2-node-run-20260519.md` exists, but T9 records that `openclaw node run` was not executed.
|
|
- Secret check: no likely secret values found; matches are placeholders or policy references.
|
|
- Role-misdirection check: prior incident is recorded as recovered; no current role/workspace mismatch found.
|
|
- Freeze/config risk check: no current evidence of frozen website risk, service persistence, `openclaw node install/start`, Nginx/Docker/website change, firewall/network change, VPS approval, node start, token handling by CORRECTION, or other configuration mutation.
|
|
- Decision: fresh guard PASS for sync/secret/role/freeze/config risks. This PASS does not unblock T9 by itself; ORCHESTRATOR must explicitly release T9. T10 remains blocked until matching non-secret T9 identity evidence exists.
|
|
- 2026-05-19 14:50 UTC+8: CORRECTION ran G2 pre-flight guard check after `git pull`.
|
|
- Role/workspace confirmed: CORRECTION in `D:\openclaw-control-plane`.
|
|
- Note: requested `tasks/T13-G2-preflight-guard.md` does not exist; this actual T13 guard file is `tasks/T13-G2-correction-guard.md`.
|
|
- G2 status confirmed: authorized and `In Progress`.
|
|
- T13 status confirmed: `ready`.
|
|
- T9 status confirmed: `ready`.
|
|
- T10 status confirmed: `blocked` until T9 produces one matching non-secret pairing request ID or pending node ID.
|
|
- PC heartbeat confirmed present, fresh, and `clean`: `2026-05-19T14:51:14+08:00`.
|
|
- VPS heartbeat confirmed present, fresh, and `clean`: `2026-05-19T14:51:04+0800`.
|
|
- Sync error check: no `sync-state/error-*.md` files present.
|
|
- Secret check: no likely secret values found; matches are placeholders or policy references.
|
|
- Role-misdirection check: prior incident is recorded as recovered; no current role/workspace mismatch found.
|
|
- Freeze/config risk check: no current evidence of frozen website risk, service persistence, `openclaw node install/start`, Nginx/Docker/website change, firewall/network change, VPS approval, node start, or other configuration mutation.
|
|
- Decision: pre-flight guard passes. Continue monitoring; allow only T9 under `docs/G2_RUNBOOK.md`; keep T10 blocked until matching non-secret T9 identity evidence exists.
|
|
|
|
## Stop Conditions
|
|
|
|
- Heartbeat older than the sync policy threshold.
|
|
- Any sync error file exists.
|
|
- Any evidence, handoff, task, commit, or chat contains a secret value.
|
|
- Any G2 task attempts service persistence, restart/reload, Nginx/Docker edits, firewall/network changes, public port exposure, or website-affecting changes.
|
|
- Pairing request identity is ambiguous.
|
|
|
|
## Acceptance
|
|
|
|
ORCHESTRATOR reviews CORRECTION findings before accepting G2 or opening G3.
|
|
|
|
## Session Freeze - 2026-05-19 14:46 UTC+8
|
|
|
|
- Status at freeze: ready.
|
|
- Next owner: CORRECTION.
|
|
- Single next action: monitor G2 guardrails while PC_EXECUTOR performs T9.
|
|
- Block G2 if sync becomes unhealthy, any secret appears, pairing identity is ambiguous, role/workspace mismatches, runbook drift occurs, or freeze-policy risk appears.
|