GPT Review — DOT-119 P0 Report and Next Directive

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

• knowledge/dev/laws/dieu44-trien-khai/reports/dot119-repair-p0-readonly-mapping-report.md
• Opus summary in conversation

Verdict

P0 PASS. Agent report is complete and read-only. Do not proceed to P1 DDL yet.

Agent fulfilled P0 scope:

• zero mutation;
• 3 new fields absent;
• fn_birth_registry_auto hash captured: 1f729b3571a74963089bb3ef388217f3;
• birth triggers count: 30;
• birth_registry rows: 75,450;
• DOT-119 stale v1 confirmed by grep=1;
• full mapping for 166 collection_registry rows;
• all parsed trigger args verified;
• all confidence = high;
• IU/UV manual classifications included with provenance.

Key findings

F1 — Schema/migration tool found

P0 found multiple schema/migration tools, especially:

• DOT-063 dot-schema-apply
• DOT-067 dot-schema-diff
• DOT-068 dot-schema-ensure
• DOT-074 dot-schema-registry-collections-ensure

Therefore P1 cannot assume raw DDL yet. Need read-only inspection of DOT-074 and related schema tools before choosing the DDL channel.

F2 — Mapping is deterministic

Current distribution:

• column: 25
• synthetic_id: 1 (information_unit)
• legacy_id_single_colon: 3
• subordinate: 1 (unit_version)
• disabled: 60
• unclassified: 76

All confidence high.

F3 — Edge policy decisions before P1 seed

Before seed, decide:

1. Views v_registry_counts, v_registry_summary: should be disabled.
2. birth_registry itself: should be disabled for self-trigger prevention.
3. 76 other unclassified rows: should remain unclassified; do not inflate 18b scope.
4. Directus fields: verify/TD after DDL, no manual directus_fields insert.

GPT decisions

Decision A — DDL channel

Do not decide raw DDL yet.

Next step is P1a — Schema Tool Inspection:

• inspect DOT-074 source;
• inspect DOT-063/067/068 only enough to determine if any is appropriate for adding columns;
• determine whether to use existing tool, extend tool, or raw DDL with explicit authorization.

No DDL until P1a report is reviewed.

Decision B — views

v_registry_counts and v_registry_summary should be classified as disabled unless P1a finds a stronger existing view strategy.

Rationale: views are not born entities and cannot have birth triggers.

Decision C — birth_registry self

birth_registry should be classified as disabled for 18b.

Rationale: self-birth trigger would loop or create governance confusion. Existing two triggers on birth_registry are not entity-birth triggers and should not imply self-birth.

Decision D — 76 unclassified

Keep remaining unclassified rows as unclassified.

Rationale: 18a rev4 intentionally requires STOP/remediation for unclassified. Do not silently default them.

Decision E — Directus fields

After DDL, verify Directus visibility. If missing, log TD/follow-up. Do not manual insert directus_fields in 18b unless a separate approved path exists.

Next directive

Opus should not draft P1 DDL+seed yet. First create a focused P1a read-only prompt/report:

knowledge/dev/laws/dieu44-trien-khai/prompts/18b-p1a-schema-tool-inspection-prompt.md

Purpose: determine legal/technical DDL channel for the 3 collection_registry fields.

P1a must:

1. Read controlling docs:

   • 18a rev4;
   • 18b rev3;
   • P0 report;
   • Đ36/collection protocol if path exists;
   • DOT-074 source and related schema tool sources.

2. Inspect read-only:

   • /opt/incomex/dot/bin/dot-schema-registry-collections-ensure
   • /opt/incomex/dot/bin/dot-schema-apply
   • /opt/incomex/dot/bin/dot-schema-diff
   • /opt/incomex/dot/bin/dot-schema-ensure
   • relevant help/usage if available.

3. Answer:

   • Can DOT-074 add columns to collection_registry, or only ensure table/known schema?
   • Does any schema tool support arbitrary ADD COLUMN safely?
   • Would using/altering DOT-074 be lower risk than raw DDL?
   • Does any tool embed outdated assumptions that could clobber schema/function/data?
   • What exact DDL channel should P1 use?

4. Output:

   • recommendation: use existing tool / extend tool first / raw DDL with approval;
   • evidence snippets from tool source;
   • STOP conditions for P1.

5. Upload report:

   • knowledge/dev/laws/dieu44-trien-khai/reports/dot119-repair-p1a-schema-tool-inspection-report.md

Hard boundaries:

• read-only only;
• no DDL;
• no UPDATE/INSERT/DELETE;
• no script rewrite;
• no DOT execution except --help/read-only inspection;
• no IU trigger;
• no IU rows;
• no Pack 2B.

Current state

P0 is accepted. The next actual action is P1a schema-tool inspection, not P1 DDL.