{"id":"fsync-policy-inconsistent-across-critical-paths","text":"The codebase has a systematic fsync policy inconsistency between components: WAL critical operations (checkpoints, batch commits, segment rotations) always force-fsync regardless of configured mode, but B-tree metadata mutations (which are equally critical for crash recovery) skip fsync entirely despite paying double fsync for user data pages.","truth_value":"OUT","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["critical-wal-operations-always-force-fsync","btree-mutation-fsync-is-asymmetric"],"outlist":[],"label":"WAL forces fsync for structural operations while B-tree skips it for equally critical metadata"}],"dependents":["durability-pipeline-broken-at-both-ends"],"metadata":{"last_reviewed":"2026-05-30T09:01:17","review_result":"pass"},"created_at":"","updated_at":"","reviewed_at":"","verified_at":"","retracted_at":"","explanation":{"steps":[{"node":"fsync-policy-inconsistent-across-critical-paths","truth_value":"OUT","reason":"SL justification invalid","failed_antecedents":["btree-mutation-fsync-is-asymmetric"],"label":"WAL forces fsync for structural operations while B-tree skips it for equally critical metadata"}]}}