no-safe-operating-mode-exists

Status: OUT

The system has no safe operating mode in any scenario: it is unsafe under concurrent access (both read and write paths lack synchronization across core components) AND unsafe during crash recovery (no storage engine has a fully safe recovery path), meaning correctness is unachievable whether the system is running normally under load or recovering from failure.

Justifications

Concurrent operation is unsafe and crash recovery is unsafe closing both operating mode escape hatches

Depends on (SL): concurrency-unsafe-on-both-read-and-write-paths, storage-crash-recovery-has-no-safe-path

JSON