GPT Directive to Opus — P3D Multidimensional Entity DB Design v2 Operational Contract

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

0. Verdict

Design v1 is directionally good but not approved as the foundational contract yet. Patch to v2 with an operational Entity Living DB contract.

Open:

P3D_MULTIDIMENSIONAL_ENTITY_DB_DESIGN_V2_OPERATIONAL_CONTRACT

1. Required reading

knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-p3d-multidimensional-entity-db-design-v1-not-approved-2026-05-12.md
knowledge/dev/laws/dieu44-trien-khai/design/p3d-multidimensional-entity-db-architecture-design.md
knowledge/dev/laws/dieu44-trien-khai/design/p3d-phase5c2-impact-addendum-after-multidimensional-design.md
knowledge/dev/laws/dieu44-trien-khai/principles/p3d-terminology-and-multidimensional-entity-db-principle-2026-05-12.md
knowledge/dev/laws/terminology-glossary.md
knowledge/dev/laws/dieu26-pivot-law.md
knowledge/dev/architecture/composition-level-law.md

Do not search broadly.

If exact relation-pair vocabulary cannot be recovered from the required docs, use targeted search only for:

Entity Living DB relations dependencies who uses me I use who belongs to me I belong to who 6 relation pairs

2. Target outputs

Patch design in place:

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

Patch addendum in place:

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

Create patch report:

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

3. Required fixes

3.1 Correct current facts

Fix 33 species hiện tại to distinguish:

law/glossary historical example = 33
live runtime from recent probes = 40

Do not use stale counts as current truth.

3.2 Tighten terminology

Use:

Tầng = architecture tier
Lớp = composition class
Layer = UI/Pivot navigation layer
Loài = species / meta-class outside 6 lớp
Entity Living DB = DB sống của thực thể

Avoid casual meta-layer except as glossary quote.

3.3 Add operational Entity Living DB contract

For each heading:

Identity
Relations
Dependencies
History
Labels
Metrics

Define:

runtime sources
minimum birth/migration requirement
enrichment path
not-cache/not-hardcode rule
impact on 5C2

3.4 Add relation-pair matrix

Recover exact old wording where possible. At minimum map:

Tôi thuộc ai?
Ai thuộc tôi?
Tôi dùng ai?
Ai dùng tôi?
Tôi chứa ai?
Ai chứa tôi?

If exact six-pair set is not found, label as NEEDS_TARGETED_AGENT_READONLY_SEARCH, not guessed.

3.5 Add matrix dimension registry contract

Define design-only contract for dimension metadata:

dimension_id
dimension_name
source_table/source_query
applies_to
cardinality
is_pivotable
is_birth_required
is_enrichment_dimension
is_ui_filterable
owner_law

No DB implementation yet, but design must state that future matrix dimensions are metadata rows, not code branches.

3.6 Split runtime gap statuses

Runtime gap matrix must have:

concept
law/design source
runtime artifact
status = VERIFIED_LIVE | DESIGNED_ONLY | MISSING | DEFERRED | UNKNOWN
evidence path/report
impact on 5C2

3.7 Reframe unit_version

Change from universal claim:

unit_version = hạ nguyên tử

To:

Current P3D IU policy: unit_version behaves as subordinate/hạ-nguyên-tử-like artifact for birth/species purposes because it has no birth trigger and is subordinate to information_unit.

3.8 Downgrade 5C2 resume claim

Change:

No runtime gap blocks pilot; no inventory needed; 5C2 can resume

To:

No broad inventory appears necessary, but 5C2 may only resume after v2 design review. A targeted preflight/inventory remains allowed if GPT identifies unresolved runtime assumptions.

3.9 Add Pivot/registries clarification

Clarify:

old registries/counting implementation = reference/draft where incomplete
operating path = PG-first Pivot, pivot_definitions, pivot_count, metadata rows
Nuxt renders only

4. Do not do

• Do not patch 5C2 prompt.
• Do not dispatch Agent.
• Do not write DB.
• Do not add DDL.
• Do not create implementation prompt yet, except noting whether a targeted read-only inventory may be needed.

5. Expected Opus response

Return only:

1. Patched design path.
2. Patched addendum path.
3. Patch report path.
4. Top 9 v2 fixes.
5. Whether targeted read-only inventory is recommended before 5C2.

6. Status

design_v2_patch_allowed=true
phase5c2_migration_allowed=false
agent_dispatch_allowed=false