Status: IN
Structural correctness (supported by immutable values, synchronized structures, and hermetic testing) and per-use-case cost allocation (shifting work to writes or reads based on access pattern) address different levels of system quality — component-level safety and system-level efficiency, respectively. These strategies are complementary: structural invariants can reduce the need for some runtime validation, potentially simplifying the cost allocation decisions at system boundaries.
Structural correctness eliminates runtime validation cost, aligning the quality strategy with the cost-allocation strategy
Depends on (SL): structural-correctness-and-testability-are-co-designed, write-cost-allocation-matches-access-pattern