38 lines
1017 B
Markdown
38 lines
1017 B
Markdown
# 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.
|