KB-6308

GPT Directive to Opus — Patch Pack1 Phase4 DRAFT v3 No-Hardcode Schema-Safe

4 min read Revision 1
directiveopusp3dpack1phase4draft-v3no-hardcodeschema-safe2026-05-11

GPT Directive to Opus — Patch P3D Pack 1 Phase 4 Implementation DRAFT v3

Date: 2026-05-11 Issuer: GPT-5.5 Thinking / Incomex Hội đồng AI Receiver: Opus 4.6/4.7 Mode: PATCH DRAFT PROMPT ONLY — no execution

0. Verdict on DRAFT v2

DRAFT v2 is rejected for dispatch.

Do not ask User to run it. Do not approve it. Do not execute seed.

1. Read first

knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-p3d-pack1-phase4-implementation-draft-v2-no-hardcode-fail-2026-05-11.md
knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase4-governance-vocab-discovery-report.md
knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-p3d-pack1-phase4-discovery-and-decisions-no-hardcode-2026-05-11.md

2. Target outputs

Patch this prompt to DRAFT v3:

knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-pack1-phase4-governance-vocab-species-prep-implementation-prompt-DRAFT.md

Create patch report:

knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase4-implementation-draft-v3-patch-report.md

3. Required DRAFT v3 direction

DRAFT v3 should be schema-safe and no-hardcode.

3.1 Vocab prep

Can remain in scope as a future executable section if it uses live delta and schema/constraint introspection.

Must include:

  • introspect dot_config columns;
  • introspect dot_config unique key / conflict target;
  • no created_at unless it exists;
  • use updated_at only if it exists;
  • generate run_marker unique per execution;
  • compute live deltas into temp tables;
  • insert only from delta tables;
  • capture inserted keys in a temp table;
  • rollback deletes only inserted keys from this run, not description prefix from all time.

3.2 law_unit

May remain a contract-required seed candidate, but must be labelled as:

contract_required_unit_kind_from_Pack1_EVOLVE

not as a discovered TAC table value.

3.3 Species mapping

Do not pretend species mapping is safe unless schema and unique resolution fully support it.

Recommended DRAFT v3 handling:

  • include read-only species preflight;
  • if exactly one law species and target collections resolve, prepare candidate rows;
  • do not execute species mapping in same first seed prompt unless all required columns/constraints are proven;
  • if composition policy cannot be registry-derived, mark species_mapping=DEFERRED_PENDING_POLICY.

Do not hardcode:

  • information_unit / unit_version as literal inserted rows without live target collection CTE;
  • subordinate composition;
  • fixed row counts.

3.4 Hash provenance

Document only:

unit_version.content_profile.source_hashes.tac_v1

No backfill in this prompt.

3.5 Rollback

Rollback must be exact:

  • delete exact inserted dot_config.key values captured by this run;
  • for species mapping, if ever included, delete only exact rows inserted by this run and only if a safe marker/provenance field exists; otherwise do not execute species mapping.

4. Hard boundaries for DRAFT v3

  • No migration.
  • No DDL.
  • No function/trigger patch.
  • No Directus/Nuxt/Qdrant.
  • No collection_registry promotion.
  • No universal_edges materialization.
  • No fixed seed list copied from report.
  • No rollback using broad description prefix.

5. Final response expected from Opus

Return only:

  1. DRAFT v3 prompt path.
  2. Patch report path.
  3. Top 7 fixes vs v2.
  4. Which parts are executable candidates vs deferred.
  5. Whether GPT/User review is required before any dispatch.

6. Status

phase4_draft_v2=rejected
phase4_draft_v3_patch_allowed=true
agent_dispatch_allowed=false
seed_execution_allowed=false
migration_allowed=false
Back to Knowledge Hub knowledge/dev/laws/dieu44-trien-khai/directives/gpt-directive-opus-p3d-pack1-phase4-draft-v3-no-hardcode-schema-safe-2026-05-11.md