GPT Review — Entity Enrichment Preflight + Current Description Write Path

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

• knowledge/dev/laws/dieu44-trien-khai/reports/entity-enrichment-deployment-preflight-report.md rev 1
• knowledge/dev/laws/dieu44-trien-khai/design/14-description-policy-endpoint-and-execution-design-pack.md rev 2
• Prior evidence: du-thao-entity-enrichment-master-fix30.md, description enrichment guide, prior Gemini enrichment context

Verdict

Agent preflight PASS, but interpretation must be corrected.

The report proves only this:

The planned entity_enrichment master system is not deployed.

It does not mean:

The system has nowhere to write descriptions.

User is correct: Gemini previously wrote descriptions. The current operational write path is direct write to source entity description fields via Directus/API, guided by description-enrichment-guide.md, with provenance updated from PROV-DOT to PROV-AI/HUMAN where applicable.

Correct model

There are currently two different concepts:

1. Current deployed description write path

• Description content lives on source entity tables that have a description column.
• Gemini/Agent enrichment has previously written directly to those source tables.
• This is operational today.
• It is the current practical place where description can be written.

2. Planned Entity Enrichment Master

• entity_enrichment table, HC-ENRICH, DOT-ENRICH, enrichment_pk_map are absent.
• This master/mirror architecture remains draft/not deployed.
• It is the intended future SSOT for detailed enrichment content, not the current deployed path.

3. Description Policy

• description_policy is not a description content field.
• It is an enforcement/routing policy indicating whether a collection/entity class requires detailed description, is structured-exempt, or is unclassified.
• It should inform both the current direct-write flow and future entity_enrichment master flow.

What file 14 rev2 still needs to clarify

File 14 rev2 is conceptually close, but it must avoid any wording that can be read as “no description write place exists.” It should state:

• Current deployed write path: source entity description columns.
• Historical Gemini enrichment used that path.
• Future intended master: entity_enrichment, not deployed.
• description_policy routes enforcement/enrichment scope; it does not replace either path.

Law / Constitution check

No blocker conflict in report or corrected interpretation.

• Đ3: current source-entity description and future enrichment master are both part of Description Governance evolution.
• Đ4: birth guard still operates on source entity rows/description today.
• Đ43/H11: current H11a/H11b scan source entity descriptions/provenance today.
• Điều 20/NT15: preflight before execution was correct.
• HP NT9: user’s correction prevents an overbroad inference from a narrow preflight.

Directive to Opus/Ocus

Patch file 14 to rev3 with a narrow wording correction, not a new design.

Required changes:

1. Add a subsection after §2B.3:

§2B.3A — Current deployed description write path

Content:

• The current deployed place to write description is the source entity description column where such column exists.
• Prior Gemini enrichment wrote descriptions directly to source entities via Directus/API and provenance updates.
• Therefore, “entity_enrichment absent” does not mean “no description write path.”
• It means the future master/mirror enrichment architecture is not deployed.

2. Update §2B.4 four-layer model wording:

• Layer 1 should be explicitly called: Current deployed source-entity description path.
• Layer 2: Future planned enrichment master, absent runtime.
• Layer 3: Description Policy routing/enforcement.
• Layer 4: IU structured-exempt rows.

3. Update §2B.6 wording:

• Option 1 remains valid only as policy/routing endpoint.
• It must route both:
  • current direct-source enrichment flow; and
  • future entity_enrichment flow when/if deployed.

4. Add a caution:

• Do not claim “system has no place to write description.”
• Correct claim: “entity_enrichment master is absent; current direct source-entity description path exists.”

Do not change the option recommendation yet unless this wording correction reveals a conflict. No DDL, no law patch, no function/trigger edits, no Pack 2B.

After rev3 upload, GPT/User can decide whether file 14 is ready for final execution-pack review or whether to first revisit the broader Entity Enrichment Master roadmap.