1.3 KiB
1.3 KiB
T13 - G2 Correction Guard
Status
draft
Owner
CORRECTION
Dependencies
- G2 user authorization recorded by ORCHESTRATOR
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.jsonandsync-state/heartbeat-vps.jsonare present and fresh before G2 execution starts. - Confirm no
sync-state/error-pc.mdorsync-state/error-vps.mdfile exists. - 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.cloudwebsite output. - Record findings in
handoff/CORRECTION.mdand, if needed, update this task status toblocked.
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.