openclaw-control-plane/tasks/T11-G2-PC-verify.md

T11 - G2 PC Evidence Verification

Status

draft

Owner

PC_VERIFIER

Dependencies

• T9 produces evidence/pc-g2-node-run-YYYYMMDD.md
• User explicitly authorizes G2 execution before T9 runs
• CORRECTION confirms sync-health is not blocked

Scope

Independently verify PC-side G2 evidence after PC_EXECUTOR runs the foreground node task.

This task is evidence review by default. It does not authorize PC mutation, service installation, service start/stop/restart, firewall changes, network changes, scheduled task changes, environment persistence, or public port exposure.

Planning Status

• G2 pre-execution plan is documented in docs/G2_RUNBOOK.md.
• This task remains draft until T9 evidence exists.
• Planning confirmation does not authorize verifier-side PC commands.

Required Evidence

• Review docs/G2_RUNBOOK.md.
• Review PC_EXECUTOR evidence from T9.
• Confirm the node command targeted openclaw.smartmotor.cloud and foreground mode.
• Confirm the token value is absent from evidence, handoffs, logs, commits, and chat.
• Confirm no openclaw node install, start, restart, stop, uninstall, firewall, network, scheduled task, environment persistence, or public-port exposure change was performed.
• Confirm PC-side evidence is synchronized through Git and visible to the VPS side.
• Write findings to evidence/verify-pc-g2-YYYYMMDD.md.
• Update handoff/PC_VERIFIER.md.

Command Drafts

Do not run PC commands during planning. By default, verification is evidence review only:

Review PC evidence only. Do not execute PC commands unless a later user instruction explicitly authorizes verifier-side read-only checks.

Stop Conditions

• T9 evidence is missing, incomplete, or not synchronized.
• Evidence contains a secret.
• Evidence shows service persistence, firewall/network mutation, public port exposure, or command drift from docs/G2_RUNBOOK.md.
• PC node identity cannot be tied to the intended Gateway pairing.

Acceptance

PC_VERIFIER may mark T9 accepted only after non-secret evidence is sufficient. ORCHESTRATOR decides whether PC-side G2 is ready to count toward G2 completion.

T11 - G2 PC Verification

Status

draft

Owner

PC_VERIFIER

Dependencies

• T9 done

Scope

Independently verify PC-side G2 evidence before ORCHESTRATOR accepts the PC half of G2.

Required Evidence

• Review evidence/pc-g2-node-run-YYYYMMDD.md.
• Confirm PC foreground node connected to the expected Gateway.
• Confirm token value is absent from evidence and handoffs.
• Confirm no openclaw node install, start, restart, stop, uninstall, service, scheduled task, firewall, network, environment persistence, or public-port exposure mutation occurred.
• Write verification evidence to evidence/verify-pc-g2-YYYYMMDD.md.
• Update handoff/PC_VERIFIER.md.

Stop Conditions

• Missing PC executor evidence.
• Evidence includes secrets.
• PC node command or Gateway target does not match docs/G2_RUNBOOK.md.
• Evidence suggests a G4 persistence action occurred during G2.

Acceptance

ORCHESTRATOR may count the PC half of G2 as accepted only after PC_VERIFIER records acceptance.