{"id":"read-path-anticipates-concurrent-flush","text":"Both `get()` (line 254) and `range_scan()` (line 286) check `_immutable_memtables` in the correct order, indicating the read path was designed for a concurrent-flush architecture that the write path never implements","truth_value":"IN","source":"entries/2026/05/29/topic-immutable-memtable-gap.md","source_url":"","source_hash":"","justifications":[],"dependents":[],"metadata":{},"explanation":{"steps":[{"node":"read-path-anticipates-concurrent-flush","truth_value":"IN","reason":"premise"}]}}