GPT Review S191 — P10D Assembly Recovery Plan v0.1 and next repo-inspection directive

Date: 2026-04-30
Phase: TAC MVP / P10D
Verdict: Recovery direction is correct. Next step must be repo inspection / route-connection probe only, not implementation.

---

1. Correction accepted

User's framing is correct:

• P10D is not a greenfield Nuxt app.
• The validated TAC data already exists in PG.
• TAC tables are already exposed as Directus collections from G8B/Gate B.
• At least one document has already been reconstructed cleanly and can be viewed as a static artifact on Nuxt/KB path.
• The immediate goal is to connect existing official TAC publications into an existing reader/tree route, separated from old KB draft view.
• Assembly First means inventory/reuse before proposing new code.

---

2. Evidence and caveat

Evidence already available:

• P10B complete: 3 publications / 86 units / 0 content drift.
• D35 clean reconstructed artifact path exists under Nuxt/KB route: https://vps.incomexsaigoncorp.vn/knowledge/dev/laws/dieu38-trien-khai/reports/p10a-2c-d35-human-render/d35-reconstructed-clean.md
• Gate B/G8B reports show 14 tac_* Directus collections registered.
• Assembly First / Red Zone require PG → Directus → Nuxt, no direct PG from Nuxt and no business logic in Nuxt.

Caveat:

• The claim that DocsTreeView + buildDocsTree exist and are used by /docs must be verified from repo paths, not assumed from memory or summary.
• KB search did not independently surface those exact symbols. Agent must inspect repo to confirm file paths and usage.

---

3. Decision

Proceed with a focused repo/API inspection prompt.

Do not write a new architecture brief and do not implement yet.

The next task is to answer one practical question:

What is the smallest existing route/component/API connection needed to show TAC publications in a new separated official URL, reusing PG → Directus → Nuxt assembly?

---

4. Required next prompt for Agent / Opus

Opus should dispatch/read-only prepare the following repo-inspection task.

Task title

P10D-0 — Assembly Route Inventory: connect TAC publications to existing Nuxt/Directus reader path

Scope

Read-only repo + API inspection. No code changes. No DDL/DML. No Directus permission/schema changes.

Mandatory checks

1. Confirm existing document/static render path

   • Verify the D35 reconstructed artifact URL/path exists and how Nuxt serves it.
   • Determine whether this is static markdown/file serving, KB route, or existing markdown reader.

2. Confirm existing tree component

   • Search repo for DocsTreeView, buildDocsTree, KnowledgeTreeView, /docs route.
   • Report exact file paths.
   • Report props/input shape.
   • Report whether it is Agency OS / existing component or local custom component.
   • Report whether it can accept TAC flat rows with minimal mapping.

3. Confirm current /knowledge/laws route

   • Locate page file.
   • Identify current data source (governance_docs etc.).
   • Identify whether route can add a separate section/link for official TAC publications without disrupting KB draft view.

4. Confirm Directus TAC API shape

   • Using existing Directus SDK/API pattern only, test read-only access to:
     • tac_publication
     • tac_publication_member
     • tac_logical_unit
     • tac_unit_version
   • Report whether relations/deep read can fetch publication → members → LU → UV.
   • Report whether ordering by render_order is possible through Directus API.

5. Confirm minimal official URL pattern

   • Propose the simplest separate URL, for example:
     • /knowledge/official-laws
     • /knowledge/laws/official
     • /laws
     • or existing route-compatible alternative.
   • Must not break current KB draft /knowledge/laws behavior.

6. Confirm no-new-code or minimal-assembly path

   • Rank:
     • A: pure existing component + Directus collection read;
     • B: minimal route config/wiring using existing Directus SDK and existing component;
     • C: PG view exposed through Directus, gate needed;
     • D: custom Nuxt code, last resort.
   • If proposing B/C/D, provide evidence why simpler option fails.

Output

Create KB report:

knowledge/dev/laws/dieu38-trien-khai/reports/p10d-0-assembly-route-inventory-2026-04-30.md

Report must include:

• repo file paths;
• API test outputs or screenshots/logs;
• component input shape;
• current route behavior;
• recommended minimal path;
• explicit “do not implement yet” STOP.

---

5. Boundaries for Opus

Do not authorize implementation from the recovery plan alone.

Next deliverable is evidence, not code.

Implementation can be authorized only after P10D-0 inventory proves which existing bridge is real and smallest.

---

6. User-facing model to preserve

The conceptual model is correct:

• KB remains draft/document archive.
• PG/TAC publications become official structured documents.
• Nuxt should show official TAC publications under a separate clean URL/path.
• The first official view is still document-based assembly, not topic graph.
• Later topic/folder/KG views can be built from the same PG units, but not now.