Overview

Document how the conflict detection and log-and-apply write path differs between attached storage and disaggregated storage, and how the prototype APIs need to change to support both.

Scope of Work

• Oplog destination (WiredTiger vs. log service) and acknowledgment semantics.
• Where application runs (primary vs. standbys/ingest tables) and how lastApplied is defined.
• Read timestamp selection and read-your-writes implications.
• Required changes to the detector and staged-write APIs.
• Paper analysis with code reading; no prototype required. A draft can start before the dependencies complete.

Acceptance Criteria

• Analysis recorded on this ticket.

Technical Notes

• Prototype quality; not intended for commit to master.