Status: IN
Reading has side effects across multiple domains: KV get triggers read repair (pushing non-dominated versions back to stale replicas), and email get unconditionally marks messages as read — observation modifies state as an unavoidable consequence, making "read-only" a leaky abstraction throughout the codebase.
Two independent domains (distributed KV, email) both attach mandatory side effects to read operations, showing that reads-with-side-effects is a cross-cutting pattern rather than a domain-specific quirk
Depends on (SL): kv-read-repair-on-get, email-service-get-email-marks-read