{"id":"range-scan-lacks-safety-guarantees","text":"Range scans are vulnerable to three independent failure modes: concurrent modifications produce inconsistent results (no snapshot isolation), corrupted sibling pointers can cause infinite traversal (no cycle guard), and large result sets consume unbounded memory (eager materialization into a list).","truth_value":"OUT","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["range-scan-no-concurrency-protection","range-scan-no-cycle-guard","range-scan-materializes-results"],"outlist":[],"label":"Three distinct safety gaps each independently threaten range scan correctness or availability"}],"dependents":["concurrency-unsafe-on-both-read-and-write-paths"],"metadata":{"last_reviewed":"2026-05-30T09:01:17","review_result":"pass"},"created_at":"","updated_at":"","reviewed_at":"","verified_at":"","retracted_at":"","explanation":{"steps":[{"node":"range-scan-lacks-safety-guarantees","truth_value":"OUT","reason":"SL justification invalid","failed_antecedents":["range-scan-no-cycle-guard"],"label":"Three distinct safety gaps each independently threaten range scan correctness or availability"}]}}