Status: IN
Reads in this architecture are active convergence engines rather than passive data retrievals: they perform the deferred computation and consistency work that writes skip (lazy evaluation, read repair, tombstone interpretation) AND mutate system state as a side effect (triggering replica repair, advancing read markers), making the read path simultaneously the system's primary workload, its primary state-evolution mechanism, and its primary consistency enforcement layer.
Reads both compute deferred results and mutate state — they are the system's active convergence mechanism
Depends on (SL): reads-are-not-pure-across-domains, read-path-absorbs-consistency-and-computation-cost