GPT Final Directive S191 — P10D No-Nuxt-Code Assembly/Config First

Date: 2026-04-30
Phase: TAC MVP / P10D
Purpose: Final prompt for Opus after User clarified: do not modify Nuxt code by default; use Directus/Nuxt assembly/config first.

---

Prompt to Opus

Opus, stop the previous direction that assumed editing web/pages/knowledge/laws/index.vue as the next step.

User clarified the governing principle:

Directus and Nuxt have already been assembled to work together. There is no reason to code in Nuxt unless every existing configuration/registry/assembly path is proven impossible. Nuxt code edits create downstream bugs and are not a root fix.

Your next task is not implementation and not a Nuxt code prompt.

Your next task is:

P10D-2A — No-Nuxt-Code Assembly Path Check for /knowledge/laws

1. Goal

Find the smallest no-Nuxt-code way to show official TAC law documents under:

https://vps.incomexsaigoncorp.vn/knowledge/laws

using the already-working path:

PG TAC data → Directus collections/API → existing Nuxt/Agency OS assembly/config

Do not propose editing Nuxt code unless you prove no registry/config/Directus-driven path exists.

---

2. Already proven — do not redo

Do not re-check these as open questions:

• D35/D32/D28 are already in PG/TAC.
• 3 publications / 86 units round-trip PASS, 0 content drift.
• Public Directus READ now works on:
  • tac_publication
  • tac_publication_member
  • tac_logical_unit
  • tac_unit_version
• Existing components/assets were found:
  • DocsTreeView
  • buildDocsTree
  • markdownToHtml
  • current /knowledge/laws route.

This task is only to find whether /knowledge/laws can be assembled/configured without editing Nuxt code.

---

3. Non-negotiable rules

3.1 No Nuxt code by default

Do not write or dispatch any prompt that modifies:

web/pages/knowledge/laws/index.vue
web/components/*
web/composables/*
web/utils/*
web/server/*

unless this task proves no assembly/config path exists and User/GPT explicitly approves an exception later.

3.2 Assembly First order

Check in this order:

1. Existing Directus data/config/collection records.
2. Existing registry/module records, if any.
3. Existing dynamic page/collection view mechanisms.
4. Existing /docs or /knowledge route configuration mechanisms.
5. Existing DirectusTable/DocsTreeView assembly through config.
6. Only after all above fail: document why a Nuxt code exception would be necessary.

3.3 Forbidden in this task

• No Nuxt code edits.
• No new server route.
• No direct PG from Nuxt.
• No custom renderer.
• No new component.
• No DDL/DML.
• No unrelated Directus mutations.
• No governance_docs mutation unless explicitly evaluated as config option and approved later.

---

4. What to inspect

Run read-only repo/API inspection on VPS via SSH.

4.1 Directus/registry-driven page mechanisms

Find whether the app already supports page/section/menu/view registration through Directus or registries.

Search for:

table_registry
DirectusTable
registry
page_registry
section_registry
navigation
menu
agent_views
docs tree
knowledge sections
governance_docs

Questions:

1. Is /knowledge/laws built from static Vue logic or registry/config?
2. Are its three current sections configurable from Directus records?
3. Can a new section “Official TAC Laws / Tài liệu chính thức” be added via Directus/config record only?
4. Is there an existing dynamic collection view that can list tac_publication without Vue edits?
5. Is there an existing docs/tree route that can be pointed to TAC Directus data by config?

4.2 Existing /docs and tree assembly

Inspect how /docs works:

1. Does it read from Agent Data/KB API, Directus, or config?
2. Is tree data passed by props/config or hardcoded in a page?
3. Can the existing tree route accept a new source/collection through config?
4. Can official TAC publications be represented as nodes using existing folder/path model without code?

4.3 Existing menu/navigation configuration

Inspect whether URL/menu/sidebar entries are stored in Directus or config.

Questions:

1. Can /knowledge/laws navigation point to an existing dynamic view without editing code?
2. Can official TAC law folder hierarchy be represented using existing menu/folder records?
3. Is there already a collection-driven detail page pattern for documents?

4.4 Directus collection view capability

Since Public READ is now open, check whether Directus/Nuxt already has a generic collection viewer for collections.

Questions:

1. Can tac_publication be listed using existing DirectusTable/table_registry?
2. Can tac_publication_member be displayed as child rows through existing relation/table capabilities?
3. Can the document reader be approximated through existing Markdown/document view without code?

---

5. Required output

Create KB report:

knowledge/dev/laws/dieu38-trien-khai/reports/p10d-2a-no-nuxt-code-assembly-path-check-2026-04-30.md

Report must include:

5.1 Evidence table

Area inspected	Existing mechanism found	File/collection/registry evidence	Can use without Nuxt code?	Notes

5.2 Options ranked by constitution compliance

Option	Description	Nuxt code edit?	Directus/config only?	Feasible?	Evidence
A	Add Official TAC Laws via existing Directus/registry config	No	Yes	?
B	Use existing dynamic collection/table/docs view	No	Yes	?
C	Add Directus config/menu/navigation record	No	Yes	?
D	Minimal Nuxt page wiring	Yes	No	Last resort only

5.3 Recommendation

Recommend the simplest no-code path if one exists.

If no no-code path exists, do not recommend code immediately. Instead write:

1. exactly what assembly/config paths were checked;
2. why each failed;
3. what tiny missing platform capability would remove the need to edit Nuxt;
4. whether that missing capability should be added to Directus/registry instead of page-specific code.

---

6. Language to use in report

Use this framing:

/knowledge/laws is the official home for PG/TAC law documents. KB is draft/legacy during migration. P10D must reuse Directus/Nuxt assembly. Nuxt code edits are not allowed by default because they create non-root fixes. This task checks whether the existing registry/config/view system can expose TAC publications without touching Nuxt code.

---

7. STOP

STOP after uploading the report.

Do not implement.
Do not edit Nuxt.
Do not mutate Directus config unless separately authorized.
Do not draft a code prompt yet.