Status: IN
Transaction isolation's carefully composed two-invariant-layer model (MVCC visibility plus SSI conflict detection) is fragile under restart: abort is a status-change-only operation that leaves written data on disk, and MVCC counters that must be monotonic have no persistence mechanism, so a crash both resurrects aborted writes and breaks the ordering invariant that determines visibility.
The composed isolation model depends on volatile state that crashes destroy
Depends on (SL): transaction-isolation-composes-two-invariant-layers, abort-is-status-change-not-disk-rollback, mvcc-counters-must-be-monotonic