GPT Review — P3D Multidimensional Entity DB Design v2 Partial Approval; Needs v3 TAC→UI Baseline Tightening

Date: 2026-05-12 Reviewer: GPT-5.5 Thinking / Incomex Hội đồng AI Reviewed:

• knowledge/dev/laws/dieu44-trien-khai/design/p3d-multidimensional-entity-db-architecture-design.md rev2
• knowledge/dev/laws/dieu44-trien-khai/design/p3d-phase5c2-impact-addendum-after-multidimensional-design.md rev2
• knowledge/dev/laws/dieu44-trien-khai/reports/p3d-multidimensional-entity-db-design-v2-operational-contract-patch-report.md

Verdict

Design v2 is a major improvement and is partially approved as the direction.

However, it is not yet approved as the final foundational contract because three items must be patched before 5C2 can resume:

1. TAC→UI deployment status is contradictory / overclaimed.
2. TAC→UI baseline verification must be required before migration, not merely optional.
3. “6 lớp + 1” terminology must avoid confusion caused by “Lớp 0 hạ nguyên tử.”

Phase 5C2 migration remains paused.

What is accepted

1. Terminology has been substantially tightened.
2. Entity Living DB now has an operational contract for the 6 headings: Identity, Relations, Dependencies, History, Labels, Metrics.
3. Relation-pair matrix based on Điều 21 is much better and usable.
4. Matrix dimension registry contract is directionally correct.
5. Runtime gap matrix now separates status and adds TAC→UI preservation columns.
6. Old registries/counting vs PG-first Pivot has been clarified.
7. TAC→UI preservation has been added explicitly and correctly in principle.
8. UI cutover is correctly deferred to a separate future pack.

Required fixes for v3

1. Fix TAC→UI deployment language

Design/report currently imply P10D-2B was deployed:

P10D-2B deployed / commit 5ce3437 deployed Laws Page code

But the same documents also say CI deploy status is UNKNOWN.

Patch wording to:

P10D-2B implementation exists at commit 5ce3437, but production deploy status remains UNKNOWN until targeted baseline verification.

Do not use “deployed” for production unless the targeted check proves it.

2. Make TAC→UI baseline verification REQUIRED before 5C2 migration

Opus currently says the two TAC→UI checks are recommended and not IU prerequisites.

GPT decision: they are not IU schema prerequisites, but they are migration safety prerequisites because 5C2 must prove it does not disturb current TAC→UI.

Before any 5C2 migration dispatch, require a targeted read-only baseline:

P3D_PACK1_TAC_UI_BASELINE_READONLY_CHECK

It must verify:

• whether commit 5ce3437 / P10D-2B is deployed in production or not;
• whether /knowledge/laws and /knowledge/laws/[pubId] are live and renderable;
• whether current UI still reads TAC tables;
• whether Đ35 current TAC render baseline can be captured for later comparison;
• no UI changes, no DB writes.

If deploy status remains unknown, 5C2 may still proceed only if the design explicitly states the UI is not live and TAC→UI preservation risk is limited. But this must be a GPT/User decision, not Opus assumption.

3. Clarify “6 lớp + 1” vs “Lớp 0”

The user’s terminology is:

6 lớp + 1 loài = atom → building + loài

The design currently writes:

Lớp = 7 (0→6) + meta

This may be technically useful but conflicts with the user’s “6 lớp + 1” phrasing.

Patch to:

Primary terminology: 6 lớp + 1 loài = nguyên tử/atom → công trình/building + loài.
Hạ nguyên tử / subordinate artifact is a policy category used for objects like unit_version in current P3D IU policy; it is not counted as one of the six primary lớp in the user-facing terminology.

Do not label the system as “7 lớp + meta.”

4. Separate UI Layer from Entity Living DB wording

The design correctly says Entity Living DB is “Lớp 3 page concept,” but because this is a dangerous term collision, patch to:

Entity Living DB is the entity detail page / living database concept. Do not call it “Lớp 3” in operational prompts unless quoting the glossary; use “Entity Living DB” instead.

5. Tighten relation-pair evidence status

If exact Điều 21 wording was recovered, cite the source path/section in the design/report. If not, mark the matrix as:

OPUS_RECONSTRUCTED_FROM_DIEU21_NEEDS_SOURCE_LINE_VERIFICATION

Do not claim “exact text recovered” without evidence path.

Required next action

Patch v2 → v3 and create a TAC→UI baseline read-only prompt DRAFT.

Open:

P3D_MULTIDIMENSIONAL_ENTITY_DB_DESIGN_V3_TAC_UI_BASELINE

Status

design_v2=PARTIAL_APPROVAL_DIRECTION_ONLY
design_v3_required=true
phase5c2_migration_allowed=false
tac_ui_baseline_check_required_before_5C2=true
ui_cutover_allowed=false
agent_dispatch_allowed=false_until_baseline_prompt_review