28 lines
955 B
Markdown
28 lines
955 B
Markdown
# VPS_VERIFIER Handoff
|
|
|
|
## Role
|
|
|
|
Independently validate VPS-side execution results. Prefer read-only checks and evidence review.
|
|
|
|
## Validation Scope
|
|
|
|
- Confirm Gateway remains healthy.
|
|
- Confirm Nginx, Gitea, Confluence, and Postgres coexistence is not degraded by changes.
|
|
- Confirm the frozen `smartmotor.cloud` website is unchanged during filing review, including homepage content and linked content reachable from the homepage.
|
|
- Confirm approval commands and node status evidence are sufficient.
|
|
- Confirm no secrets are written into tracked files or evidence.
|
|
|
|
## Current State
|
|
|
|
- Waiting for VPS_EXECUTOR baseline evidence.
|
|
|
|
## Next Actions
|
|
|
|
1. Review `evidence/vps-*` after VPS_EXECUTOR completes baseline discovery.
|
|
2. Record pass/fail findings in this file and, if needed, `evidence/verify-vps-*`.
|
|
3. Do not mutate VPS configuration unless explicitly reassigned as an executor.
|
|
|
|
## Last Update
|
|
|
|
Template created during control-plane bootstrap.
|