GPT Correction S191 — P10D deploy direction must respect VPS as code/runtime SSOT

Date: 2026-04-30
Phase: P10D
Correction: Prior wording that centered GitHub/CI as the source path is misaligned with current operating reality. VPS is the code/runtime SSOT under Điều 41.

---

1. Law/evidence

Relevant KB evidence:

• knowledge/dev/laws/dieu41-luat-van-hanh-ma-vps-v1.1.md states Điều 41 is enacted and applies while VPS is the operating SSOT, with a single VPS sharing code + production data.
• knowledge/current-state/reform-PG-tools/01-kien-truc.md states VPS is SSOT for source/runtime; GitHub is a push/deploy pipe, not runtime SSOT.

---

2. Correction

Previous direction:

Push commit to GitHub → trigger deploy-vps.yml → runtime verify.

This may be incomplete or misleading because current work is performed on VPS and VPS is SSOT.

Correct framing:

Source of truth is the VPS repo/runtime. First inspect the VPS deployment mechanism, then activate the already-committed VPS change through the approved VPS path. GitHub/CI is only one possible pipe if the repo/pipeline is configured that way.

---

3. Revised next step

Replace P10D-2C — Deploy Commit 5ce3437 via CI with:

P10D-2C — Activate VPS SSOT Commit 5ce3437 and Runtime Verify

Scope:

1. No new feature code.
2. Confirm VPS repo state and commit 5ce3437.
3. Inspect how current Nuxt .output is built/deployed from VPS SSOT.
4. Use the existing approved deployment/build path only.
5. If that path is GitHub Actions, report why GitHub is just the pipe and ensure VPS SSOT is not overwritten/lost.
6. If local VPS build is the approved path, run only existing documented commands.
7. Runtime verify /knowledge/laws, D35 reader, and KB legacy route.
8. Report PASS/FAIL to KB.

---

4. Boundary

Do not assume GitHub is SSOT.
Do not git pull/reset/checkout blindly.
Do not overwrite VPS changes.
Do not make new code changes in deployment step.
Do not mutate Directus/DB.
If deploy mechanism is unclear, STOP and report exact evidence.