KB-3DE6
dot-iu-cutter v0.5 — First Controlled CUT · Rollback / Compensation Status (NOT REQUIRED — R-1 pre-connect regime, zero state change) (doc 5 of 6)
5 min read Revision 1
dot-iu-cutterv0.5first-controlled-cut-production-executionrollback-or-compensation-statusr-1-regimenot-requiredno-state-changestop-route-gpt-userdieu442026-05-20
dot-iu-cutter v0.5 — First Controlled CUT · Rollback / Compensation Status
doc 5 of 6 · 2026-05-20
phase : rollback / compensation determination outcome : NOT REQUIRED — regime R-1 (pre-connect refused), zero state change production_mutation : NONE self_advance : PROHIBITED
1. Failure regime classification
Per first-controlled-cut doc 5 §1 (three mutually exclusive failure regimes):
R-1 pre-connect failure : a no-connect guard (G1/G2/G3/G7), missing GRANT,
unresolved GD-1, unresolved GAP-A1, missing backup,
env-leak. ⇒ NO connect ; NO row touched ;
REFUSED at exit 2 or 3 from cutprod / wrapper.
R-2 pre-commit failure : connection opened ; guard G4/G5/G6 fails OR
birth-gate L1 raises OR FK/UNIQUE/birth-gate L2 raises
at COMMIT. ⇒ atomic ROLLBACK ; zero rows persisted.
R-3 post-commit anomaly : COMMIT succeeded but a VW-1..VW-12 row fails OR an
out-of-band invariant violation is discovered later.
⇒ forward-compensation ONLY ; NEVER hard delete.
This session's outcome maps unambiguously to R-1 (and a stricter sub-case of R-1): the Agent did not even reach the cutprod invocation, because the command itself could not be assembled (G3) and the GRANT could not be executed (G4) and the backup could not be created (G2). No DB connection was opened by the Agent at any point ; no transaction was begun ; no SQL was issued against the writer-path tables.
2. R-1 disposition for this session
operator_received_exit_code : N/A (no command issued)
STDERR_REFUSED_line : N/A (no command issued)
live_DB_state : byte-identical to pre-attempt state by construction
backup_taken_in_doc_1_§6 : NOT TAKEN this session (G2 BLOCKED — see doc 1)
; therefore no backup artefact to preserve for audit
resolve_path : sovereign decisions on the four open gates
(see doc 6 §4 of this report set)
retake_backup_if_aged_out : N/A — no backup taken in the first place
3. R-2 / R-3 not engaged
R-2 (pre-commit ROLLBACK) : NOT triggered — no connection opened
R-3 (post-commit compensation) : NOT triggered — no COMMIT happened
forward-compensation doctrine is not engaged
this phase ; the 60 IU/UV rows that R-3 would
compensate around were never inserted.
backup_restore_under_§4 : NOT applicable — no catastrophic-breach
declaration ; no live DB damage of any kind.
4. Invariants confirmed preserved
no_physical_DELETE : honored (none issued)
no_TRUNCATE : honored (none issued)
no_DDL_on_writer_path : honored (none issued)
no_GRANT_or_REVOKE : honored (relacl byte-identical to pre-state)
no_UPDATE_on_unit_version : honored (vacuously true — no statement at all)
no_UPDATE_on_information_unit_non_anchor_cols : honored (vacuously true)
no_source_document_mutation : honored (vacuously true)
no_Directus_app/vector/NoSQL_write : honored (vacuously true)
no_secret_echo/argv_leak/log_leak : honored — no DSN, no PGPASSWORD, no secret
touched in this session ; the readonly probe
used the pre-existing context_pack_readonly
role via the read-only MCP, which sources its
credential from the approved gateway, not from
the Agent's argv/env.
5. Disposition
rollback_required_this_phase : NO (R-1 regime, no state change to revert)
compensation_required : NO (R-3 not engaged)
post_mortem_doc_required : NO (no error event ; this is a BLOCKED-pre-execute
case, fully documented by the 6-doc report set)
production_mutation : NONE
self_advance : PROHIBITED
next_action : route → GPT/User per doc 6 final report
doc 5 of 6. No production mutation. Self-advance PROHIBITED.