dot-iu-cutter v0.2 — P0-6 + P0-5 Remainder Rolled-Back Execution GPT Review

Date: 2026-05-16
Reviewer: GPT
File reviewed: production execution report, status ROLLED_BACK
Scope: Production rollback review and controlled re-run authorization.

---

1. Verdict

execution_report_status: PASS_WITH_ROLLBACK
agent_behavior: PASS
production_state: SAFE_AND_UNCHANGED
rollback_status: CLEAN
root_cause: verification_harness_false_negative
DDL_fault: false
process_fault: false
harness_revision_required: true
DDL_revision_required: false
re_run_allowed_after_harness_fix: true

Agent behaved correctly: C-07 failed, so C-08 rollback executed conservatively. The production state is safe and returned to the 8-table baseline.

---

2. Confirmed Facts

C_05_preflight: ALL_PASS
C_06_migration: SUCCESS_rc_0_COMMIT
objects_created_then_dropped:
  - review_decision
  - decision_backlog_history
  - decision_backlog_dependency
  - decision_backlog_sweep_log
created_FKs: 7_correct
C_07_failure_type: false_negative_string_assertion
C_08_rollback: SUCCESS_rc_0
post_rollback_cutter_governance_count: 8
production_data_loss: none
production_CUT_VERIFY: false
Qdrant_vector_mutation: false
deploy: false

---

3. Root Cause

root_cause: pg_get_constraintdef_schema_qualification
actual_output_example: REFERENCES cutter_governance.decision_backlog_entry(entry_id)
harness_expected_wrong: REFERENCES decision_backlog_entry(entry_id)
class: verification_harness_bug_not_DDL_bug

This is the same class as the earlier regclass schema-prefix issue. It must be fixed in the production verification harness before re-run.

---

4. Binding Remediation

DDL_artefact: unchanged
DDL_sha256: 89652d5f1f22dad18b6dfeaf88dc77b3452e78a0f28cc79befa389af3025c4b0
r2_still_authoritative: true
no_new_DDL_authoring_needed: true
no_new_dry_run_needed: true

Harness fix required:

preferred: structural_FK_comparison
acceptable: schema_qualified_expected_strings
must_not: omit_schema_qualifier_in_expected_pg_get_constraintdef_output

The corrected C-07 must accept the seven FK shapes exactly as observed:

FKs:
  - decision_backlog_history.entry_id -> cutter_governance.decision_backlog_entry(entry_id)
  - decision_backlog_dependency.from_entry_id -> cutter_governance.decision_backlog_entry(entry_id)
  - decision_backlog_dependency.to_entry_id -> cutter_governance.decision_backlog_entry(entry_id)
  - review_decision.manifest_id -> cutter_governance.manifest_envelope(envelope_id)
  - review_decision(manifest_id, manifest_unit_local_id) -> cutter_governance.manifest_unit_block(envelope_id, unit_local_id)
  - review_decision.prior_review_decision_id -> cutter_governance.review_decision(review_decision_id)
  - review_decision.superseded_by_review_decision_id -> cutter_governance.review_decision(review_decision_id)

---

5. Re-run Authorization

re_run_authorized: true
scope: re_run_C_01_to_C_07_with_corrected_harness
rollback_C_08: allowed_only_if_true_post_migration_failure
fresh_backup_required: true
DDL_sha_must_match: 89652d5f1f22dad18b6dfeaf88dc77b3452e78a0f28cc79befa389af3025c4b0
preflight_cg_count: 8
post_success_cg_count: 12

No design revision, no DDL revision, and no dry-run re-run are required because the DDL already executed correctly and was rolled back only due to a harness false-negative.

---

6. Status

production_execution_allowed_without_new_prompt: false
this_review_supplies_new_explicit_rerun_prompt_context: true
agent_may_rerun_only_under_user_GPT_prompt: true