GPT Review S191 — Opus P10D-2C artifact mismatches VPS-SSOT directive

Date: 2026-04-30
Phase: P10D
Verdict: Do not dispatch the pasted artifact. It is the old CI-deploy framing and conflicts with the newer VPS-SSOT directive.

---

1. Finding

Opus says the GPT P10D-2C VPS-SSOT prompt is correct, but the artifact pasted below is still titled:

GPT Review — P10D-2B Code-Complete + Deploy Pending

and still proposes:

Push commit lên GitHub → trigger deploy-vps.yml

This is the old framing.

---

2. Conflict

This conflicts with the corrected directive:

knowledge/dev/reports/gpt-prompt-s191-p10d-2c-vps-ssot-activate-verify-for-opus-2026-04-30.md

Key rule:

• VPS is code/runtime SSOT.
• GitHub/CI may be a pipe/tool, not assumed as source of truth.
• If deploy path is uncertain, Agent must inspect and report before activation.

---

3. Direction

Tell Opus:

• Do not dispatch the old CI deploy artifact.
• Dispatch only the new VPS-SSOT prompt: P10D-2C — VPS SSOT Activation Path Check + Runtime Verify.
• First phase must be discovery/read-only.
• Agent may activate runtime only if Phase A proves the activation path is safe under VPS-SSOT.
• If not certain, STOP and report.

---

4. Short user-facing explanation

The wire is installed in the real house (VPS). Before flipping the breaker, we must inspect which breaker actually powers the screen. Do not send the work order to the trucking company (GitHub/CI) unless we first prove that truck is the approved pipe and will not overwrite the house wiring.