GPT Directive to Opus — P3D Pack 1 Phase 4C Prompt rev2 No-Hardcode Selectors

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

0. Verdict

Phase 4C design direction is accepted, especially the finding that fn_birth_registry_auto does not use discriminator columns.

The current dry-run prompt is not approved for dispatch because it still contains hardcoded species selectors and leaves too much to Agent improvisation.

Patch to prompt rev2.

1. Required reading

knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-p3d-pack1-phase4c-design-direction-ok-prompt-not-approved-no-hardcode-2026-05-11.md
knowledge/dev/laws/dieu44-trien-khai/design/p3d-pack1-phase4c-species-mapping-strategy-qt001-backfill-design.md
knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-pack1-phase4c-readonly-dryrun-species-mapping-qt001-prompt.md
knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase4c-species-mapping-strategy-design-report.md

2. Target outputs

Patch design wording in place:

knowledge/dev/laws/dieu44-trien-khai/design/p3d-pack1-phase4c-species-mapping-strategy-qt001-backfill-design.md

Patch prompt in place:

knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-pack1-phase4c-readonly-dryrun-species-mapping-qt001-prompt.md

Create patch report:

knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase4c-prompt-rev2-no-hardcode-selector-patch-report.md

3. Required design wording changes

Downgrade any recommendation such as:

SPE-GOV primary now + migration-time species assignment

to:

Option/hypothesis pending dry-run evidence and GPT/User decision

Do not lock SPE-GOV, SPE-LAW, a new species, or migration-time correction yet.

4. Required prompt changes

4.1 Remove hardcoded species selectors from executable/dry-run logic

Do not use fixed selectors such as:

code='SPE-GOV'
code='SPE-LAW'
species_code='law'
species_code='governance_infra'

unless explicitly labelled as Phase 4B snapshot labels and re-verified live before use.

4.2 Use source-derived species candidate categories

Dry-run categories should be generated from live data:

1. observed/governance-infrastructure-like species candidates, discovered by live fields and existing mappings;
2. law-domain species candidates, discovered by live fields and existing mappings;
3. existing species already mapped to governance/birth/meta registries;
4. new-species scenarios parameterized by live discovered composition levels, not a fixed atom/molecule/compound list.

4.3 Make information_unit explicit as scoped target

If the prompt uses information_unit, it must state:

This is the scoped Pack 1 target collection, not a schema guess.

If possible, verify the target exists in collection_registry before dry-run.

4.4 Replace “Agent implements queries” with deterministic requirements

The prompt may remain mission-style, but each goal must include:

• authoritative source;
• selector rule;
• skip/STOP condition;
• output shape.

Do not leave room for Agent to choose fuzzy selectors as production evidence.

4.5 New species scenarios

Do not hardcode atom, molecule, compound as the only options unless derived from live entity_species.composition_level distinct values or Điều 0-B. Prefer:

SELECT DISTINCT composition_level FROM entity_species

then dry-run scenarios for each discovered composition level, labelled candidate_not_approved.

4.6 Discriminator finding must stay explicit

Keep the critical finding:

fn_birth_registry_auto currently ignores discriminator columns.

Therefore discriminator mapping is design/dry-run only unless a future function patch or migration-time correction mechanism is approved.

5. Hard boundaries

• No agent dispatch.
• No DB write.
• No seed.
• No backfill.
• No migration.
• No DDL.
• No function patch.
• No species decision locked.
• No composition decision locked.
• No hardcoded species/layer counts.

6. Expected Opus response

Return only:

1. Patched design path.
2. Patched dry-run prompt path.
3. Patch report path.
4. Top 7 no-hardcode selector fixes.
5. Confirmation GPT/User review required before dispatch.

7. Status

phase4c_prompt_rev1=not_approved
phase4c_prompt_rev2_patch_allowed=true
agent_dispatch_allowed=false
seed_allowed=false
backfill_allowed=false
migration_allowed=false