Status: IN
Financial systems combine domain-appropriate concurrency control (pessimistic locking for wallets, optimistic locking for hotels) with write-read asymmetry (irrevocable ledger entries, reconciling balance derivation) to support end-to-end correctness: concurrency control prevents write-time corruption while structural asymmetry supports read-time consistency — provided the read path does not depend on assumed invariants that are never enforced in code, which would undermine the reconciliation that reads are supposed to perform.
domain-specific concurrency strategies and codebase-wide write-read asymmetry are complementary, not redundant
Depends on (SL): concurrency-safety-strategy-varies-by-financial-risk, write-read-asymmetry-is-end-to-end-correct