Status: OUT
The entire storage stack uses rigid binary formats that preclude both forward evolution and post-corruption recovery: WAL records are contiguously packed with no block alignment or version negotiation preventing resync after mid-file corruption, and SSTables lack per-entry checksums and efficient skip structures — neither layer can be upgraded in place or self-repaired after partial damage.
Two depth-1 conclusions about different storage layers independently identify the same structural rigidity pattern, revealing it as a cross-cutting architectural property rather than a per-component oversight
Depends on (SL): wal-binary-format-prevents-evolution-and-recovery, sstable-format-lacks-integrity-and-efficiency-mechanisms