Status: IN
Message delivery guarantees enforced at the consumer side instantiate the architecture's broader read-path responsibility pattern: just as KV reads absorb convergence (repair) and computation (lazy evaluation), message consumers absorb delivery semantics (at-least-once vs exactly-once) through their own poll/commit behavior, keeping the write/publish path simple and coordination-free.
Consumer-side delivery guarantees are a specific case of read-path absorbing complexity
Depends on (SL): message-delivery-guarantees-are-consumer-side, reads-are-active-convergence-engines