GPT Addendum — Gemini Direct Description Write Path for File 14 rev3

Date: 2026-05-04 Reviewer: GPT-5.5 Thinking / Incomex Hội đồng AI Trigger: User emphasized that Gemini had already written descriptions, so the system must not be described as having no place to write description.

Additional evidence

Opus searched prior context and confirmed:

• Gemini enrichment pilot wrote descriptions directly to source entity tables such as entity_species.description, tasks.description, dot_tools.description, etc.
• Write path used Directus REST API.
• Provenance labels were updated from PROV-DOT to PROV-AI.
• The workflow queried PROV-DOT entities from v_entity_full_classification, read metadata/templates from description-enrichment-guide.md, wrote new description, then updated provenance.
• This did not use entity_enrichment, because that master table is still draft/not deployed.

Correct interpretation

There is already a deployed description write path:

Source entity description columns + Directus/API updates + provenance labels.

entity_enrichment is not the existing write path. It is a future master/mirror upgrade design.

Therefore, the sentence “entity_enrichment absent = no place to write description” is false.

Correct sentence:

entity_enrichment master is absent, but the current direct source-entity description write path exists and has been used by Gemini/Agent.

Impact on File 14

No need to change the overall strategy yet:

• description_policy is still needed as policy/routing layer.
• It should govern both the current direct source-entity enrichment flow and the future entity_enrichment master flow.
• IU rows remain structured-exempt candidates.

But file 14 must be patched to rev3 with this correction.

Directive

Patch file 14 rev3 narrowly:

1. Add/strengthen §2B.3A — Current deployed description write path.
2. Explicitly cite Gemini pilot/direct write path:
   • source entity description columns;
   • Directus REST API;
   • PROV-DOT → PROV-AI;
   • no entity_enrichment used.
3. Update four-layer model:
   • Layer 1 = current deployed source-entity description write path;
   • Layer 2 = future planned entity_enrichment master, absent runtime;
   • Layer 3 = description_policy routing/enforcement;
   • Layer 4 = IU structured-exempt rows.
4. Keep Option 1 only as policy endpoint, not content endpoint.
5. Add explicit caution: do not say the system has no description write place.

No DDL, no runtime, no law patch, no Pack 2B.