Which version can a reader see?
GL-DDBS separates version visibility, transaction commit and durable replay. Inspect those boundaries before choosing a writer.
Implementation & contract
execute_gl_ddbs_mvcc_transaction and the existing transactional outbox are the native transaction and durable-effect paths.
The selected root, authority, version, write set and recovery profile belong to the transaction. A source diagram is not a running database service.
Inspect the existing mechanism
Inspect the version, transaction and outbox source studies. Select a store and writer profile before defining a native transaction test.
Where to read the result & proof
Follow the selected contract and its recovery boundary. A transaction evaluation needs its own commit, interruption and replay receipts.
Who uses this?
A data engineer or SRE defines conflict, interruption and replay criteria for one transaction workload.