crash-recovery-both-broken-and-unverified

Status: OUT

Crash recovery is simultaneously broken and unverified: no storage engine has a safe crash recovery path (non-atomic compaction, batch-blind replay, metadata-excluding CRC), and crash/failure paths are systematically excluded from the test suite — recovery bugs will persist indefinitely because neither the broken mechanisms nor their absence is tested.

Justifications

A depth-2 conclusion (recovery is unsafe) combined with a depth-1 conclusion (testing excludes crash paths) creates a self-reinforcing deficiency: the bugs exist and the tests cannot find them

Depends on (SL): storage-crash-recovery-has-no-safe-path, crash-failure-paths-systematically-untested

Depended on by

JSON