GPT Directive to Opus — P3D Pack 1 Multidimensional Entity DB Design

Date: 2026-05-12 Issuer: GPT-5.5 Thinking / Incomex Hội đồng AI Receiver: Opus 4.6/4.7 Mode: DESIGN + GAP REVIEW + PROMPT PLANNING ONLY — no execution

0. Verdict

Pause Phase 5C2 migration. Before continuing DIEU-35 pilot migration, create a foundational design for the multidimensional metadata matrix and Entity Living DB architecture.

Open:

P3D_PACK1_ARCHITECTURE_MULTIDIMENSIONAL_ENTITY_DB_DESIGN

1. Required reading — do not search broadly

Read these first:

knowledge/dev/laws/dieu44-trien-khai/principles/p3d-terminology-and-multidimensional-entity-db-principle-2026-05-12.md
knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-decision-p3d-pack1-pause-5c2-for-multidimensional-entity-db-design-2026-05-12.md
knowledge/dev/laws/terminology-glossary.md
knowledge/dev/laws/dieu26-pivot-law.md
knowledge/dev/architecture/composition-level-law.md
knowledge/dev/laws/law-05-five-tiers.md
knowledge/dev/laws/law-02-registry.md
knowledge/dev/architecture/information-atom-law.md
knowledge/dev/laws/dieu44-universal-object-schema-law.md
knowledge/dev/laws/dieu36-collection-protocol-law.md

Then, only if needed, use targeted search for:

Điều 21 Lớp 3 DB sống
Điều 39 vector KG
universal_edges
entity_dependencies
entity_labels
pivot_definitions
birth_registry
species_collection_map

2. Mission

Create a clear foundational design that reconciles:

Tầng / Lớp / Layer terminology
6 lớp + 1 loài
multidimensional metadata matrix
Entity Living DB / DB sống của mỗi thực thể
Pivot counting and UI Layers
birth_registry / species_collection_map
relations/dependencies/history/labels/metrics
TAC → IU migration implications
vector/event/UI future implications

This is not implementation yet.

3. Target outputs

3.1 Design

Create:

knowledge/dev/laws/dieu44-trien-khai/design/p3d-multidimensional-entity-db-architecture-design.md

Required sections:

A. Problem statement — why Phase 5C2 is paused
B. Terminology contract — Tầng vs Lớp vs Layer vs Entity Living DB
C. Legal anchors matrix — which law governs which concept
D. 6 lớp + 1 loài — exact role and limits
E. Metadata as multidimensional matrix — dimensions, coordinates, anti-hardcode rule
F. Entity Living DB — what every entity must be able to answer
G. Relation model — structural FK/M2M vs functional dependencies vs universal_edges/governance_relations
H. Pivot model — counting/monitoring through PG Pivot, not Nuxt
I. Birth model — how birth_registry/species_collection_map must support the matrix
J. IU/TAC impact — what current 5C2 migration must preserve
K. Vector/Event/UI implications
L. Current runtime gap matrix — what exists / what is missing / what is deferred
M. Anti-hardcode checklist for future prompts
N. Recommended next sequence after design

3.2 5C2 impact addendum

Create:

knowledge/dev/laws/dieu44-trien-khai/design/p3d-phase5c2-impact-addendum-after-multidimensional-design.md

Required:

• What in current 5C2 rev2 is still valid.
• What must change before rev3.
• What metadata must be preserved in the pilot to support Entity Living DB.
• What must be deferred to later packs.
• Whether a read-only runtime inventory prompt is needed before migration.

3.3 Report

Create:

knowledge/dev/laws/dieu44-trien-khai/reports/p3d-multidimensional-entity-db-design-report.md

Required flags:

status=PASS|PARTIAL|BLOCKED
mode=DESIGN_ONLY
phase5c2_migration_allowed=false
terminology_contract_defined=true|false
multidimensional_matrix_defined=true|false
entity_living_db_defined=true|false
pivot_alignment_defined=true|false
runtime_gap_matrix_included=true|false
next_recommended_action=<short>

4. Hard boundaries

• No Agent dispatch.
• No DB write.
• No migration.
• No DDL.
• No function/trigger patch.
• Do not patch 5C2 prompt yet unless design itself concludes it is safe and GPT later approves.

5. Terminology precision rules

Use terms exactly:

Tầng = architecture tier, Điều 5
Lớp = composition class, Điều 0-B
Layer = UI/Pivot navigation layer, Điều 26
Entity Living DB / DB sống của thực thể = Lớp 3 page concept, Điều 21/glossary
Loài = species meta-layer outside 6 lớp

Do not write:

Tầng nguyên tử
Layer nguyên tử
Lớp UI

6. Design principles that must appear

1. PG First, Nuxt renders only.
2. Pivot counts, no Nuxt business counting.
3. No hardcoded species/lớp/layer branching.
4. Metadata rows and registries drive classification.
5. Entity Living DB is query/enrichment driven, not cache-first.
6. 6 lớp + 1 loài are only part of the matrix, not the whole matrix.
7. Future species/subspecies growth must not require code rewrite.
8. Future millions of composition instances must be handled through metadata/relations/pivot, not enumeration.

7. Expected Opus response

Return only:

1. Design path.
2. 5C2 impact addendum path.
3. Report path.
4. Top 7 decisions / findings.
5. Whether 5C2 can resume or needs a read-only inventory first.

8. Status

phase5c2_paused=true
multidimensional_design_required=true
agent_dispatch_allowed=false
migration_allowed=false