{"id":"transaction-recovery-has-no-crash-path","text":"Transaction abort is a status-change-only operation with no disk rollback, and MVCC correctness depends on monotonic counters that have no persistence mechanism, meaning a crash simultaneously leaves aborted-transaction writes on disk and resets the ordering counters that determine visibility — both invariants fail together.","truth_value":"IN","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["abort-is-status-change-not-disk-rollback","mvcc-counters-must-be-monotonic"],"outlist":[],"label":"Both abort cleanup and ordering invariants exist only in volatile memory"}],"dependents":[],"metadata":{},"created_at":"","updated_at":"","reviewed_at":"","verified_at":"","retracted_at":"","explanation":{"steps":[{"node":"transaction-recovery-has-no-crash-path","truth_value":"IN","reason":"SL justification valid","antecedents":["abort-is-status-change-not-disk-rollback","mvcc-counters-must-be-monotonic"],"label":"Both abort cleanup and ordering invariants exist only in volatile memory"},{"node":"abort-is-status-change-not-disk-rollback","truth_value":"IN","reason":"premise"},{"node":"mvcc-counters-must-be-monotonic","truth_value":"IN","reason":"premise"}]}}