{"id":"commit-conflict-check-not-atomic","text":"The conflict-check-then-commit sequence in `MVCCDatabase.commit()` is not atomic — no locking protects the window between checking versions and marking committed, requiring single-threaded execution for correctness.","truth_value":"IN","source":"entries/2026/05/29/snapshot-isolation-mvcc_database-commit.md","source_url":"","source_hash":"","justifications":[],"dependents":[],"metadata":{},"explanation":{"steps":[{"node":"commit-conflict-check-not-atomic","truth_value":"IN","reason":"premise"}]}}