recovery-simultaneously-over-and-under-engineered

Status: OUT

Recovery is paradoxically both over-engineered and under-implemented: the WAL builds complete sequence number and checkpoint infrastructure that's never consulted during replay, while the actual recovery paths lack batch atomicity and metadata CRC protection — engineering effort was invested in infrastructure that goes unused while the active recovery path remains unsafe.

Justifications

Vestigial recovery infrastructure coexists with unsafe actual recovery paths

Depends on (SL): wal-recovery-infrastructure-is-vestigial, storage-crash-recovery-has-no-safe-path

Depended on by

JSON