39 lines
1.1 KiB
Markdown
39 lines
1.1 KiB
Markdown
# T6 - Verify VPS Baseline
|
|
|
|
## Status
|
|
|
|
draft
|
|
|
|
## Owner
|
|
|
|
VPS_VERIFIER
|
|
|
|
## Dependencies
|
|
|
|
- T4 done
|
|
|
|
## Scope
|
|
|
|
Independently verify VPS baseline evidence before any VPS configuration mutation.
|
|
|
|
The `smartmotor.cloud` filing-review freeze is a hard constraint throughout verification.
|
|
|
|
## Required Evidence
|
|
|
|
- VPS baseline evidence reviewed and accepted or returned with findings.
|
|
- Confirmation that VPS_EXECUTOR did not accept its own work.
|
|
- Confirmation that no homepage content, linked page content reachable from the homepage, static assets, Nginx routing, Docker bind mounts, container images, service state, or `/opt/services/docker-composite.yml` entries were changed.
|
|
- Confirmation that Gateway, Nginx, Gitea, Confluence, and Postgres coexistence was only observed, not modified.
|
|
- Confirmation that evidence contains no secrets.
|
|
|
|
## Stop Conditions
|
|
|
|
- Missing evidence.
|
|
- Evidence includes secrets.
|
|
- Evidence shows drift from the mission or frozen website policy.
|
|
- Evidence suggests a required mutation before G1 has been accepted.
|
|
|
|
## Acceptance
|
|
|
|
ORCHESTRATOR may count the VPS half of G1 as accepted only after VPS_VERIFIER records acceptance.
|