GPT Analysis — Need QT-003R Retroactive Collection Registration

Date: 2026-05-04 Reviewer: GPT-5.5 Thinking / Incomex Hội đồng AI Trigger: User asked whether existing birth processes cover Pack 2A or a new process is needed.

Documents checked

• knowledge/dev/architecture/birth-procedures.md rev 4 — Quy trình Quản lý Thực thể v3.0
• knowledge/ops/processes/birth-process-v1.md rev 1 — QT-001/QT-002 older process doc
• knowledge/dev/laws/dieu44-trien-khai/design/12c-iu0-pack2a-birth-process-classification.md rev 1
• knowledge/dev/laws/dieu44-trien-khai/design/12-iu0-pack2a-dot-governance-registration-execution-pack.md rev 4

Finding

There is no need to invent an unrelated new top-level process, because birth-procedures.md v3.0 already has QT-003: Khai báo collection mới.

However, Pack 2A is not perfectly covered by QT-003 as written, because QT-003 assumes collection is being declared before use, while Pack 2A is a retroactive case:

• PG tables already exist from Pack 1.
• Tables have 0 data rows.
• They are missing collection_registry/birth_registry/meta_catalog/directus_collections.
• The action is governance readiness registration before first use.

This is best modeled as a subtype/variant of QT-003, not as QT-001 or QT-002.

Recommended process addition

Add a sub-process under QT-003:

QT-003R — Khai báo collection đã lỡ tạo nhưng chưa dùng

Scope:

• Existing PG table/collection was created before full governance registration.
• Table has 0 data rows.
• No production use yet.
• Goal is to register collection governance before first data rows are created.

Required steps:

1. Verify table exists.
2. Verify table has 0 rows. If >0 → STOP and reclassify to QT-001/backfill analysis.
3. Verify no collection_registry row or exact intended row already exists.
4. Resolve governance_role/source_kind/storage_role/migration_state/description by law/tool convention.
5. Register via legal DOT tool (dot-collection-register), not raw SQL.
6. Verify birth/registry/health outputs.
7. Declare follow-up: before data rows are created, choose QT-002 or domain-specific birth path.

Why not a fully separate top-level process?

Because the domain is collection declaration, and QT-003 already governs collection declaration. Adding QT-003R keeps the process taxonomy clean:

• QT-001 = entity rows already exist → backfill.
• QT-002 = new entity rows → birth-first.
• QT-003 = collection declaration.
• QT-003R = retroactive collection declaration before first use.

Immediate implication for Pack 2A

File 12 rev4 is conceptually right but should be amended later or the process doc should be updated to name QT-003R explicitly.

For Pack 2A execution, the existing rev4 STOP condition is sufficient:

• if IU tables have 0 rows → proceed as readiness governance registration;
• if >0 rows → STOP and reclassify to QT-001/backfill.

Structural follow-up

Process documentation should be updated so future agents do not need to infer this again. Add QT-003R to birth-procedures.md or create an ops process addendum that later gets merged into the canonical process document.