Incomex AI Portal
KB-34E7

GPT Review — File 12 Description/Birth Governance

7 min read Revision 1
gpt-reviewiu-0pack-2afile12description-governancebirthdieu3dieu4blocker

GPT Review — File 12 Description/Birth Governance

Date: 2026-05-04 Reviewer: GPT-5.5 Thinking / Incomex Hội đồng AI Reviewed file: knowledge/dev/laws/dieu44-trien-khai/design/12-iu0-pack2a-dot-governance-registration-execution-pack.md rev 1 Trigger: User reminded that Description is mandatory at birth and must follow the actual governed form/process.

Documents checked

  • knowledge/dev/laws/dieu44-trien-khai/design/12-iu0-pack2a-dot-governance-registration-execution-pack.md rev 1
  • knowledge/dev/laws/law-03-metadata.md rev 6
  • knowledge/dev/laws/dieu3-phu-luc-description-templates.md rev 3
  • knowledge/dev/laws/law-04-birth-process.md rev 5
  • Search results for Đ43 / metadata governance and file 12 context

Verdict

PASS DIRECTION, BLOCK DISPATCH UNTIL DESCRIPTION/BIRTH CONTRACT IS VERIFIED AND PATCHED.

File 12 correctly moves Pack 2A away from raw SQL and toward legal DOT tools. However, it is not yet ready for execution because the Description/Birth contract is under-specified and partly non-compliant.

Key issue

File 12 treats description as a parameter to fill with a short ad-hoc sentence. That is not sufficient.

Per Đ3 and Đ4:

  • Description is mandatory metadata.
  • Description must satisfy C1–C4: non-empty, min length, anti-gaming, Vietnamese with accents.
  • For collections, detailed description format is governed by Phụ lục Đ3 §A.3: [Vai trò governance]. Chứa [nội dung chính]. Lớp [Não/Kho/Cổng] (HP §B). Thuộc [Luật]. [Quan hệ FK chính nếu có].
  • Basic description can be auto-generated by trigger/template, but detailed description should be written deliberately when we know the context.
  • Description must be present at birth where possible; not accepted as vague placeholder.

File 12 proposed descriptions:

  • information_unit: “Bảng chứa information units — đơn vị thông tin có version, birth gate 2 lớp, identity profile. IU-0 pilot.”
  • unit_version: “Bảng version history cho information units — immutable per version, content hash, version seq.”

These are not terrible, but they do not explicitly follow the collection description format: governance role, layer, law jurisdiction, and FK/main relation are missing or incomplete.

Governance-role nuance

Opus recommends observed to avoid HC-SCHEMA false positive. This may be reasonable as a pilot/readiness state, but it must not be framed as “tạm trú để né description.”

The real reason must be:

  • IU tables are architecture/runtime data tables with IU-specific metadata in identity_profile and Pack 1 birth gates.
  • Đ36 HC-SCHEMA currently assumes governed tables need a physical description column.
  • If IU is intentionally modeled without physical description, then either:
    1. use observed during pilot/readiness with explicit upgrade condition, or
    2. amend/extend the governing schema/HC-SCHEMA/IU design so governed IU tables satisfy Description Law through an approved strategy.

This requires evidence from actual tool/runtime conventions. Do not guess.

Blockers before dispatch

  1. File 12 must include a focused Description/Birth contract section.
  2. File 12 must use compliant descriptions for the collection_registry rows being born.
  3. File 12 must verify whether dot-collection-register writes description directly, relies on auto-template, or both.
  4. File 12 must verify actual dot_config description templates for collection_registry and min-length config.
  5. File 12 must distinguish:
    • description of the collection_registry row (mandatory now), versus
    • description column/metadata strategy for future IU data rows (not solved by Pack 2A).
  6. Governance-role recommendation must be supported by runtime/HC-SCHEMA evidence, not just convenience.
  7. Rollback section currently allows raw DELETE. This should be changed to tool-supported rollback/update first; raw DELETE only if explicitly allowed by law/tool/admin fallback. Otherwise STOP.

Directive to Opus/Ocus

Do not dispatch Claude Code for write yet.

Prepare one consolidated package, not multiple microtasks:

knowledge/dev/laws/dieu44-trien-khai/design/12a-iu0-pack2a-description-birth-contract-review.md

Then patch file 12 to rev2 based on 12a.

12a must answer, with Agent/runtime evidence where needed:

  1. What is the actual dot-collection-register contract for description?

    • Does it accept --description?
    • Does it pass description into collection_registry?
    • Does it trigger fn_description_birth_guard and provenance trigger?

  2. What is the runtime Description enforcement?

    • dot_config.description_min_length
    • desc_template_collection_registry
    • fn_description_birth_guard current body/behavior
    • fn_description_context if relevant

  3. What are 5–10 examples of high-quality existing collection_registry.description rows?

    • Prefer rows with governance_role in governed and observed.
    • Extract actual convention, not invented style.

  4. What exact descriptions should be used for:

    • information_unit
    • unit_version

Descriptions must follow Phụ lục Đ3 §A.3 collection format: [Vai trò governance]. Chứa [nội dung chính]. Lớp [Não/Kho/Cổng]. Thuộc [Luật]. [Quan hệ FK chính nếu có].

  1. Governance-role decision:

    • Compare observed vs governed using actual HC-SCHEMA and Description law.
    • Clarify whether observed is a lawful pilot/readiness state, not a workaround.
    • Define explicit upgrade condition to governed if observed is recommended.

  2. IU data-row description strategy:

    • Pack 2A registers the tables, not IU data rows.
    • Still, record the unresolved design issue: IU rows have identity_profile, not physical description.
    • State whether this needs Đ44/Đ36/Đ3 alignment before governed or before production use.

  3. Rollback legality:

    • Inspect whether dot-collection-register has update/unregister/rollback support.
    • If not, rollback must STOP and request separate legal/tool decision. Do not normalize raw DELETE as routine rollback.

After 12a, patch file 12 rev2 with:

  • compliant descriptions;
  • evidence-based governance_role recommendation;
  • runtime description contract;
  • explicit distinction between collection description and IU row description strategy;
  • safer rollback section;
  • final dispatch prompt only if legal/tool path is confirmed.

Current status

Pack 2A Legal/Tooling Preflight: PASS. File 12 rev1: NOT READY FOR DISPATCH. Next: 12a Description/Birth Contract Review + file 12 rev2.

Back to Knowledge Hub knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-file12-description-birth-governance-2026-05-04.md