reads-bear-full-correctness-burden

Status: IN

Reads bear the full correctness burden: they absorb lazy computation and active repair to converge state, and must interpret metadata-as-deletion (tombstones, delete markers, soft-deleted records) to present a correct view — making the read path the primary site of system complexity across the codebase.

Justifications

Both depth-2 conclusions shift complexity to reads — one for computation/convergence, the other for deletion semantics — together establishing reads as the locus of correctness

Depends on (SL): read-path-absorbs-consistency-and-computation-cost, deletion-is-metadata-in-replicated-systems

Depended on by

JSON