dot-iu-cutter v0.1 — Production Command Review Package GPT Review

Date: 2026-05-15
Reviewer: GPT
File reviewed: knowledge/dev/laws/dieu44-trien-khai/execution/dot-iu-cutter-v0.1-p0-production-command-review-package-2026-05-15.md
Scope: Review only. No command executed by GPT.

---

1. Verdict

production_command_review_package_status: PASS_WITH_SCOPE_RESTRICTION
agent_revision_needed: false
production_execution_authorized_now: false
recommended_next_step: explicit_v0_1_subset_production_execution_prompt

The command review package is acceptable, with one binding scope restriction: v0.1 production execution may ship only the 5-table subset that was validated in the HB-05 26/26 dry-run.

---

2. Binding Scope Decision

GPT accepts the scope gap identified by Agent and agrees with Opus:

v0_1_allowed_scope:
  - decision_backlog_entry
  - dot_pair_signature
  - cut_change_set
  - cut_change_set_affected_row
  - verify_result
v0_2_deferred_scope:
  - manifest_envelope
  - manifest_unit_block
  - review_decision
  - canonical_address on tac_logical_unit
  - decision_backlog_history
  - decision_backlog_dependency
  - decision_backlog_sweep_log

Reason: only the 5-table subset has direct HB-05 dry-run evidence. Shipping tables/fields without dry-run evidence would violate the governance discipline established for this project.

---

3. Command Plan Decision

GPT accepts the proposed command plan structure:

• C-01 fresh backup;
• C-02 backup checksum;
• C-03 schema snapshot;
• C-04 row-count snapshot;
• C-05 identity/existence/DOT-pair preflight;
• C-06 DDL checksum gate;
• C-07 dry-run environment health;
• C-08 single-transaction migration with ON_ERROR_STOP=1;
• C-09 post-migration verification;
• C-10 rollback sequence;
• C-11 failure-stop wrapper.

The DDL source must remain checksum-locked to:

/opt/incomex/backups/dieu44_hb05_2026-05-15/schema/cutter_governance_dryrun_v0.1.sql
sha256: 9eb032e2d40d51a1447ad07e5039db8b8b2f83d29b600fb6388c41ec342e4208

---

4. Conditions Before Execution Prompt

Before production execution starts, the execution prompt must explicitly enforce:

1. v0.1 scope restriction to the 5 validated tables only.
2. Fresh production-bound backup less than 60 minutes before C-08.
3. Checksum verification of the DDL source.
4. Production identity preflight.
5. Abort if cutter_governance already exists.
6. Abort if DOT-pair rows 991/992 are missing or changed.
7. Single transaction for migration.
8. Post-migration verification before reporting success.
9. Rollback path available but not run unless failure triggers it.
10. No production CUT/VERIFY after schema creation.

---

5. Status

ready_for_explicit_production_execution_prompt: true
execution_authorized_by_this_review: false
v0_2_required: true
v0_2_reason: remaining P0 objects lack dry-run evidence