KB-6858

GPT Final Directive S191 — P10D Parallel TAC Screen, copy working display path, do not replace KB

6 min read Revision 1

s191p10dparallel-runkb-legacytac-officialgit-commit-requiredopus-directive

GPT Final Directive S191 — P10D Parallel TAC Screen, copy working display path, do not replace KB

Date: 2026-04-30
Phase: TAC MVP / P10D
Purpose: Correct prior “replace/bypass” wording. User clarified: run KB and PG/TAC in parallel. Copy the working display path to the new TAC source. Do not unplug/delete KB.

Prompt to Opus

Opus, adjust the P10D direction again. The previous “replace/bypass legacy laws” wording is not precise enough.

User’s correct metaphor:

Do NOT unplug the old DVD player.
Do NOT remove the old KB screen.

Copy the working cable/screen setup
and connect a parallel screen/path to the new PG/TAC DVD source.

KB remains accessible as draft/legacy.
PG/TAC becomes the new official laws screen.

This is safer and closer to the migration strategy.

1. Correct product model

1.1 KB stays alive

KB / old knowledge documents remain accessible normally:

old KB documents = draft / legacy / archive;
do not delete;
do not break existing KB routes;
do not mutate governance_docs unless separately authorized;
do not remove old /docs or /knowledge/[...slug] behavior.

1.2 PG/TAC runs in parallel

PG/TAC official laws get their own official display path:

/knowledge/laws

This path should show official TAC publications:

D35
D32
D28

using the same kind of Directus → Nuxt display machinery already proven by KB.

1.3 Migration later, not now

Only after PG/TAC official screen is stable and the rest of KB is cut into PG/TAC should the team consider deleting or retiring KB.

No deletion/retirement now.

2. Correct technical framing

This is copy/parallelize the working display path, not “replace old system.”

Use:

Existing Directus SDK pattern
Existing DocsTreeView
Existing buildDocsTree
Existing markdownToHtml/prose rendering
Existing route/nav conventions

New source:

tac_publication
tac_publication_member
tac_logical_unit
tac_unit_version

No direct PG from Nuxt. No new server route. No new renderer. No new tree component.

3. Clean up wrong direction / prevent confusion

Opus must explicitly state in the next prompt/report:

Prior “replace/bypass legacy laws” wording is corrected.
KB remains accessible.
P10D creates/uses a parallel TAC official screen/path.
Do not attempt to repair or merge old governance_docs laws UI during this MVP.
Do not delete, hide, or break old KB content.

If any earlier draft prompt says “replace/bypass legacy laws” in a way that could imply breaking KB, mark it superseded in the new prompt.

4. Next task to draft

Draft:

P10D-2B — Parallel Official TAC Laws Screen Wiring

Purpose:

Copy the already-working Directus→Nuxt display pattern and connect it to the TAC source for /knowledge/laws, while leaving the KB/draft display paths intact.

The prompt should instruct Agent to:

Gate 0: SSH VPS + repo path.
Read current git status before changes.
Create a backup or note exact files before patch.
Inspect existing KB reader pattern immediately before patching.
Implement the smallest parallel TAC official laws screen under /knowledge/laws.
Reuse existing components/functions only:
- Directus SDK/readItems;
- DocsTreeView;
- buildDocsTree;
- markdownToHtml/prose styling.
Fetch TAC data through Directus collections only.
Preserve KB routes and old knowledge reader behavior.
Verify TAC official screen:
- /knowledge/laws loads;
- D35/D32/D28 appear;
- D35 opens/readable;
- D35 node count = 36;
- no direct PG;
- no server route;
- no new tree/renderer component;
- no secrets.
Verify KB still works:

existing /docs or /knowledge/[...slug] route still loads at least one old KB document;
do not require exact full visual regression, just prove not broken.

Upload report to KB.
Commit git after successful verification.

5. Git commit requirement

Because this task changes repo code, the Agent prompt must require a git commit after PASS verification.

Required steps:

ssh contabo 'cd /opt/incomex/docker/nuxt-repo && git status --short'
# after patch + verification PASS
ssh contabo 'cd /opt/incomex/docker/nuxt-repo && git add <changed-files> && git commit -m "P10D: add parallel TAC official laws screen"'
ssh contabo 'cd /opt/incomex/docker/nuxt-repo && git status --short'

Rules:

Commit only files changed by this task.
Do not include unrelated dirty files.
If pre-existing dirty files exist, report them and avoid touching them.
If verification FAILS, do not commit. Upload failure report and stop.
If git commit is blocked by environment/config, report exact reason and leave patch uncommitted with rollback instructions.

This follows the operating rule expectation that completed repo mutations are committed after verification.

6. Boundaries

Allowed:

Minimal route/page wiring if needed to create the parallel TAC official screen.
Existing components/functions only.
Directus SDK reads from TAC collections.

Forbidden:

No direct PG from Nuxt.
No custom server route.
No new tree component.
No new markdown renderer.
No DDL/DML.
No Directus mutations.
No deleting or hiding KB routes.
No full KB migration.
No topic graph/search/admin workflow.
No unrelated code cleanup.

7. Explanation style

When explaining to User, use this metaphor:

We keep the old KB DVD player and screen running. We copy the working cable/screen setup and connect a new parallel screen to the PG/TAC DVD player. Only after the new screen is stable do we discuss retiring the old KB player.

Avoid over-technical framing unless writing Agent commands.

8. STOP

Opus should draft the P10D-2B implementation prompt and send it to GPT/User review before dispatch.

Do not dispatch implementation without approval.