GPT Directive to Opus — P3D Pack 1 Phase 5C1 rev2 Transaction-Safe Dispatch Candidate

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

0. Verdict

5C1 rev1 candidate is directionally correct but not dispatch-approved. Patch to rev2 transaction-safe dispatch candidate.

Open:

P3D_PACK1_PHASE5C1_REV2_TRANSACTION_SAFE_DISPATCH_CANDIDATE

1. Required reading

knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-p3d-pack1-phase5c1-rev1-candidate-not-approved-transaction-stop-gates-2026-05-11.md
knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-pack1-phase5c1-species-mapping-qt001-backfill-prompt-DRAFT.md
knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase5c1-rev1-dispatch-candidate-patch-report.md

2. Target outputs

Patch prompt in place:

knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-pack1-phase5c1-species-mapping-qt001-backfill-prompt-DRAFT.md

Create patch report:

knowledge/dev/laws/dieu44-trien-khai/reports/p3d-pack1-phase5c1-rev2-transaction-safe-patch-report.md

3. Required rev2 fixes

3.1 Add explicit transaction model

Add a section before write steps:

All DB writes must occur in one transaction.
If any gate or verification fails inside transaction, ROLLBACK.
No partial commit.

Write transaction should include:

1. repeated collision checks;
2. repeated mapping dedupe check;
3. target birth row capture;
4. INSERT species;
5. INSERT mapping;
6. UPDATE captured birth rows;
7. post-write verification;
8. COMMIT only after all verification passes.

3.2 Add operational stop-gate behavior

Require:

ON_ERROR_STOP=1 or equivalent
no SQL improvisation
no retry with modified query
no continuing after failed gate
report failed gate id

3.3 Split precommit capture vs committed rollback keys

Add explicit distinction:

precommit_target_capture = target list discovered before UPDATE
committed_rollback_keys = species_id + mapping_id + backfilled_birth_ids after COMMIT succeeds

Persist both in report, but label correctly.

3.4 Repeat stale-sensitive checks inside transaction

Inside transaction, immediately before INSERT/UPDATE, repeat:

species code collision
species entity code collision
mapping existence for information_unit
backfill target capture

3.5 Clarify KB/VPS persistence timing

Captured target list may be written before mutation as audit. Final committed rollback keys must be written after COMMIT.

If transaction rolls back, report attempted/precommit keys as diagnostic only.

3.6 Add rollback verification

Rollback section must include post-rollback verification:

• species row absent;
• mapping row absent;
• captured birth ids restored to pre-write values;
• no remaining side effects from this run marker.

3.7 Fix default verification wording

For status, depth, kg_metadata, and any DB defaulted field, rev2 must say:

expected default is obtained from introspection/probe;
verify actual equals resolved default;
if default differs from expected, report drift and stop before write or treat as FIELD_UNRESOLVED_STOP depending on field criticality.

Do not hardcode status='active' as an unverified assumption.

4. Do not change

Do not change locked species identity values. Do not change scope. Do not add TAC migration. Do not add unit_version mapping. Do not add DDL. Do not dispatch Agent.

5. Expected Opus response

Return only:

1. Patched 5C1 prompt path.
2. Patch report path.
3. Top 7 rev2 transaction-safety fixes.
4. Confirmation GPT final review + User GO required before Agent dispatch.

6. Status

phase5c1_rev2_patch_allowed=true
agent_dispatch_allowed=false
seed_allowed=false
backfill_allowed=false
migration_allowed=false