Incomex AI Portal
KB-298F

GPT Final Directive S191 — P10D DVD Source Swap for Official Laws

5 min read Revision 1
s191p10dofficial-lawsdvd-source-swapassembly-firstopus-directive

GPT Final Directive S191 — P10D DVD Source Swap for Official Laws

Date: 2026-04-30
Phase: TAC MVP / P10D
Purpose: Final simplified directive for Opus using User's metaphor: keep the screen/wires, swap the DVD source.

Prompt to Opus

Opus, reset the framing. Stop making this bigger than it is.

User's correct mental model:

Current working system:
DB → Directus → Nuxt = DVD player / cable / screen already working.

Old source:
knowledge_documents / governance_docs / old KB-style content.

New source:
tac_publication / tac_publication_member / tac_logical_unit / tac_unit_version.

Task:
Do not rebuild the screen. Do not redesign the cable. Swap the DVD source feeding the screen.

P10D is not a new architecture. It is a source swap for the official laws screen.

1. Correct product decision

/knowledge/laws should become the official TAC Laws screen.

The current laws page based on governance_docs should be treated as legacy/defective/old source for this purpose. Do not preserve or extend it as a requirement in P10D MVP.

Use only the existing route/button concept:

The Laws button / URL points to the new official TAC source.

Do not try to merge old governance_docs sections with TAC in the same MVP screen unless that is trivially already supported.

2. Already proven

Do not re-litigate:

  • PG/TAC has 3 official pilot documents: D35, D32, D28.
  • 86 units round-trip PASS, 0 content drift.
  • Public Directus READ works on the 4 TAC collections.
  • Existing Directus → Nuxt reading pattern works.
  • Existing tree/reader pieces exist:
    • DocsTreeView
    • buildDocsTree
    • markdownToHtml
  • Evidence shows /knowledge/[...slug] and /docs use Directus collections through SDK, not a hardcoded KB-only API.

3. Task goal

Prepare the next implementation prompt as a DVD source swap:

Replace the old /knowledge/laws content source with the official TAC source while reusing the existing Directus→Nuxt screen pattern.

The visible MVP target:

/knowledge/laws
├── Đ35
├── Đ32
└── Đ28

Selecting a document shows tree + readable content using existing components/patterns.

4. Implementation philosophy

This is allowed only as assembly/composition, not as new architecture.

Allowed:

  • reuse existing Directus SDK/readItems pattern;
  • reuse existing DocsTreeView/buildDocsTree;
  • reuse existing markdownToHtml/prose rendering;
  • point the Laws route/button to the TAC official source;
  • replace or bypass legacy laws content for MVP.

Forbidden:

  • no custom server route;
  • no direct PG from Nuxt;
  • no new renderer;
  • no new tree component;
  • no topic graph/search/admin workflow;
  • no full KB migration;
  • no attempt to fix legacy governance_docs laws page now;
  • no DDL/DML;
  • no Directus mutation unless separately authorized.

5. What Opus must do next

Draft a short implementation prompt for Agent:

P10D-2B — Swap /knowledge/laws to Official TAC Source

The prompt must instruct Agent to:

  1. Inspect current /knowledge/laws and existing Directus reader pattern one last time.
  2. Backup / record git status.
  3. Replace or bypass the old governance_docs laws content on /knowledge/laws with TAC official source.
  4. Fetch tac_publication list via Directus SDK.
  5. Fetch selected publication members via Directus SDK with LU/UV relations.
  6. Map TAC rows into the existing tree/list shape consumed by buildDocsTree / DocsTreeView.
  7. Render selected content using existing markdownToHtml / prose pattern.
  8. Keep changes minimal and local to the route/page unless the existing pattern clearly requires a child route.
  9. Do not preserve legacy laws UI as a constraint; legacy can be handled later.
  10. Verify /knowledge/laws shows D35/D32/D28 and can open/read D35 with 36 nodes.

6. Language requirement for Opus

When explaining to User/GPT, use the metaphor:

We are not building a new TV. We are not replacing the cable. We are changing the DVD source from old KB/governance docs to official TAC data.

Avoid over-technical framing unless needed for Agent commands.

7. Required verification in implementation prompt

  • /knowledge/laws loads.
  • It lists D35/D32/D28 from TAC.
  • D35 opens and displays readable content.
  • D35 tree/node count = 36.
  • Directus anonymous API is used; no direct PG.
  • No server route added.
  • No new tree/renderer component.
  • No secret exposure.
  • Rollback path documented.
  • Report uploaded to KB.

8. STOP

Opus only drafts the P10D-2B prompt for GPT/User review.

Do not dispatch implementation until approved.

Back to Knowledge Hub knowledge/dev/reports/gpt-final-directive-s191-p10d-dvd-source-swap-official-laws-2026-04-30.md