GPT Directive Addendum to Opus — Preserve Existing TAC→UI Runtime in Multidimensional Design v2

Date: 2026-05-12 Issuer: GPT-5.5 Thinking / Incomex Hội đồng AI Receiver: Opus 4.6/4.7 Applies to: gpt-directive-opus-p3d-multidimensional-entity-db-design-v2-operational-contract-2026-05-12.md Mode: DESIGN PATCH ONLY — no execution

0. Why this addendum exists

The user flagged a critical omission: P3D has already invested substantial design and implementation effort in TAC and TAC→UI. The multidimensional Entity Living DB design must not re-invent or bypass the existing working TAC→UI path.

This addendum is binding.

1. Additional governing rule

Before proposing any redesign, Opus must identify what already exists and preserve it unless there is explicit evidence that it violates law or production requirements.

Do not rebuild from scratch.
Do not discard working TAC→UI behavior.
Do not replace UI/TAC assumptions without first documenting the current runtime contract.

2. Required additional reading

In addition to the v2 directive reading list, Opus must read the existing TAC/UI-related design/runtime docs if present. Use targeted search only; do not search broadly.

Search targets:

TAC UI Laws Page Đ35 Nuxt TAC publication_member render_order laws page tree view
P10D Laws Page TAC UI render fidelity
TAC→UI existing runtime design

If exact docs cannot be found, mark:

TAC_UI_DOCS_NOT_FOUND_NEEDS_TARGETED_AGENT_READONLY_INVENTORY

Do not guess.

3. Required new section in v2 design

Add a section:

O. Existing TAC→UI runtime preservation contract

It must answer:

1. What TAC→UI path currently works?
2. Which tables/fields feed current UI?
3. Which UI behavior must be preserved during TAC→IU transition?
4. Which parts can be gradually redirected from TAC to IU?
5. What must not be changed in Nuxt/UI before IU replacement is proven?
6. What runtime evidence supports the above?
7. What remains UNKNOWN and needs a targeted read-only inventory?

4. Required additions to 5C2 impact addendum

Add a section:

6. TAC→UI preservation impact

It must classify 5C2 pilot effects:

NO_TOUCH_CURRENT_TAC_UI
PARALLEL_IU_PILOT_ONLY
UI_REDIRECT_FORBIDDEN_UNTIL_VERIFIED
TAC_SOURCE_REMAINS_CANONICAL_FOR_UI_DURING_PILOT

Meaning:

• 5C2 must not break existing TAC-driven UI.
• 5C2 pilot data may be created in IU in parallel.
• UI must not switch to IU until render fidelity and UI contract are proven.
• TAC remains the source for current UI until an explicit cutover pack.

5. Required runtime preservation matrix

Add to the runtime gap matrix these columns:

current_TAC_UI_dependency
preserve_during_pilot = true|false
cutover_allowed_now = true|false
required_cutover_evidence

For 5C2 pilot, default must be:

preserve_during_pilot=true
cutover_allowed_now=false

unless GPT/User explicitly says otherwise.

6. Required conclusion change

Opus must not conclude:

5C2 can resume and UI can consume IU

It may only conclude, if evidence supports:

5C2 can resume as a parallel IU pilot that does not affect current TAC→UI runtime.
UI cutover remains a separate future pack after fidelity verification.

7. Status

addendum_binding=true
phase5c2_migration_allowed=false
ui_cutover_allowed=false
next_action=OPUS_PATCH_DESIGN_V2_WITH_TAC_UI_PRESERVATION