{"id":"mvcc-counters-must-be-monotonic","text":"`_next_tx_id` and `_next_timestamp` must never reissue a previously used value; if they reset to 1 on restart, visibility comparisons like `created_by < tx.tx_id` silently produce wrong results by conflating old and new transaction IDs","truth_value":"IN","source":"entries/2026/05/29/topic-snapshot-disk-persistence.md","source_url":"","source_hash":"","justifications":[],"dependents":[],"metadata":{},"explanation":{"steps":[{"node":"mvcc-counters-must-be-monotonic","truth_value":"IN","reason":"premise"}]}}