read-path-absorbs-consistency-and-computation-cost

Status: IN

Multiple systems deliberately shift both computation (lazy evaluation) and convergence work (read repair) to the read path, keeping writes simple and fast at the cost of heavier, more complex reads.

Justifications

lazy eval (autocomplete decay, URL expiration, payment balance) defers computation to reads; KV read repair defers convergence to reads — the combined pattern reveals a systematic bias toward read-path complexity across the repo

Depends on (SL): lazy-read-time-evaluation-trades-write-simplicity-for-read-cost, kv-read-path-is-self-healing

Depended on by

JSON