Status: OUT
The write-to-verify durability pipeline is broken at both ends: fsync policy inconsistencies across critical paths mean data may never durably reach disk (B-tree skips fsync for structural metadata while paying double for data), and incomplete CRC coverage means corrupted data that does reach disk passes integrity checks undetected (payload-only CRC leaves routing metadata unprotected).
Inconsistent fsync leaves data unwritten; incomplete CRC leaves corruption undetected — neither end of the pipeline is reliable
Depends on (SL): fsync-policy-inconsistent-across-critical-paths, integrity-checking-is-both-incomplete-and-unrecoverable