{"id":"durability-bugs-invisible-to-testing","text":"Durability bugs are permanently invisible: the write-to-verify durability pipeline is broken at both ends (fsync policy gaps prevent data from reaching stable storage, and incomplete integrity checks cannot verify it arrived), while crash/failure recovery paths are systematically excluded from testing — the system cannot detect its own durability failures through any available mechanism.","truth_value":"OUT","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["durability-pipeline-broken-at-both-ends","crash-failure-paths-systematically-untested"],"outlist":[],"label":"A depth-3 conclusion (durability pipeline broken) combined with depth-1 (testing gaps) produces a depth-4 epistemic impossibility: durability bugs exist and no mechanism — operational or test — can surface them"}],"dependents":["silent-data-loss-is-default-operational-mode"],"metadata":{},"created_at":"","updated_at":"","reviewed_at":"","verified_at":"","retracted_at":"","explanation":{"steps":[{"node":"durability-bugs-invisible-to-testing","truth_value":"OUT","reason":"SL justification invalid","failed_antecedents":["durability-pipeline-broken-at-both-ends","crash-failure-paths-systematically-untested"],"label":"A depth-3 conclusion (durability pipeline broken) combined with depth-1 (testing gaps) produces a depth-4 epistemic impossibility: durability bugs exist and no mechanism — operational or test — can surface them"}]}}