GPT Review — File 14 Requires Entity Enrichment Master Reconciliation

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

• knowledge/dev/laws/dieu44-trien-khai/design/14-description-policy-endpoint-and-execution-design-pack.md rev 1
• knowledge/dev/laws/dieu44-trien-khai/reports/iu0-description-policy-tiering-runtime-investigation-report.md rev 1
• knowledge/dev/laws/dieu44-trien-khai/reviews/opus-assessment-agent-investigation-description-policy-2026-05-04.md rev 1
• knowledge/current-state/reports/du-thao-entity-enrichment-master-fix30.md rev 8

Verdict

File 14 is directionally useful but NOT approved for execution.

Opus correctly resolved that v_entity_full_classification.tier is DOT tier and should not be overloaded. It also reasonably identifies Option 1 as a clean endpoint if the only question is where to store per-collection Description Policy.

However, file 14 has a material omission: it does not reconcile with the prior Entity Enrichment Master design. User is correct: the system already had a designed place/process for detailed description enrichment, and Gemini/GPT council cycles had discussed/reviewed that package. File 14 currently risks reinventing or bypassing this layer.

Existing description/enrichment design found

knowledge/current-state/reports/du-thao-entity-enrichment-master-fix30.md defines a planned entity_enrichment master table:

• entity_enrichment is intended as SSOT metadata enrichment table.
• Entity gốc becomes mirror; DOT sync pushes approved enrichment back.
• Đ3 §2.7 draft says detailed description enrichment should be written to entity_enrichment, not directly to entity source.
• It includes birth seed trigger concept, enrichment PK map, HC-ENRICH-SEED/DRIFT/STALE, DOT-ENRICH-SYNC, DOT-ENRICH-VERIFY.
• It was still draft/waiting further review, not necessarily production-complete.

This confirms User's point: there is already a conceptual place for detailed descriptions. The current Pack 2B/IU problem is not simply “where to add a description_policy column”; it is how to integrate:

1. source entity base/basic description;
2. detailed enrichment master (entity_enrichment);
3. description policy tiering;
4. IU high-volume structured-exempt rows;
5. H11/birth guard behavior.

Corrected interpretation

The needed split is not only Tier A/B/C. It is also a split between:

• Base/basic description: may live on source entity/collection for architectural objects or be auto-generated.
• Detailed/enriched description: should probably live in entity_enrichment when that system is adopted.
• Description policy: a classification that tells H11/birth guard/enrichment pipeline whether detailed description is required, optional, exempt, or unknown.

Therefore collection_registry.description_policy may still be the right place for policy, but it is not the place for detailed descriptions themselves. File 14 must say this explicitly.

What file 14 did well

• Correctly rejected overloading v_entity_full_classification.tier.
• Correctly rejected Option 2/4/5 as final standalone endpoints.
• Correctly kept Pack 2B closed and no runtime action.
• Correctly identified IU data rows should be exempt from per-row free-text detailed description.

What must be corrected

C1 — Add Entity Enrichment Master reconciliation

File 14 rev2 must include a section:

§2B — Existing Entity Enrichment Master / Detailed Description SSOT

It must read and summarize:

knowledge/current-state/reports/du-thao-entity-enrichment-master-fix30.md

Answer:

• Is entity_enrichment deployed or still draft?
• What was its intended role?
• Which laws/docs did it propose to amend?
• How does it relate to Đ3 §2.5/§2.7, H11a/H11b, PROV-DOT/AI/HUMAN?
• Does description_policy belong in collection_registry, entity_enrichment, dot_config, or both?

C2 — Clarify policy vs content/enrichment

File 14 must state:

• description_policy is not the description content store.
• It only controls enforcement/routing:
  • required detailed enrichment;
  • structured-exempt;
  • unclassified/discovery.
• Detailed descriptions, when required, should flow through the approved enrichment mechanism, likely entity_enrichment, once finalized.

C3 — Adjust Option 1 recommendation

Option 1 may remain the recommended policy endpoint, but not an execution approval.

Reword:

• Option 1 = clean endpoint for per-collection policy classification.
• Entity Enrichment Master = intended endpoint for per-entity detailed description content/enrichment.
• They are complementary, not competing.

C4 — Add deployment status check for entity_enrichment

File 14 should include a read-only check or prompt to verify runtime state:

SELECT to_regclass('public.entity_enrichment') AS entity_enrichment_table;
SELECT column_name, data_type FROM information_schema.columns WHERE table_name='entity_enrichment' ORDER BY ordinal_position;
SELECT code, name, is_active FROM system_health_checks WHERE code LIKE 'HC-ENRICH%';
SELECT code, name, status FROM dot_tools WHERE code LIKE 'DOT-ENRICH%';
SELECT key, value FROM dot_config WHERE key='enrichment_pk_map';

This can be included in file 14 rev2 as a small read-only preflight. Do not dispatch unless approved.

C5 — Update execution plan sequencing

Before any DDL/function/H11 change, sequence must be:

1. Reconcile entity_enrichment status.
2. Decide whether to finalize/amend the existing enrichment master package or leave it deferred.
3. Then design description_policy enforcement.
4. Then design Pack 2B F6 birth path.

Directive to Opus/Ocus

Do not execute file 14 rev1.

Patch to 14 rev2 with Entity Enrichment Master reconciliation. Do not dispatch Agent yet. Do not DDL, do not patch laws, do not open Pack 2B.

Required reads:

• knowledge/current-state/reports/du-thao-entity-enrichment-master-fix30.md
• knowledge/dev/guides/description-enrichment-guide.md
• knowledge/dev/laws/law-03-metadata.md
• knowledge/current-state/queries/h11b-description-detail-missing
• file 13 rev3 + agent investigation report

Required output:

• Revise file 14 to distinguish:
  • policy classification endpoint;
  • detailed description/enrichment content endpoint;
  • source entity mirror/basic description;
  • IU structured-exempt rows.
• Add entity_enrichment deployment status check section/prompt.
• Re-state recommendation: likely Option 1 for policy, but coordinated with entity_enrichment for content/enrichment.

Current decision

No execution approval.

File 14 rev1 is useful but incomplete. It must be reconciled with the existing Entity Enrichment Master design before choosing final runtime changes.