https://tuladb.com/blog/ Engineering notes on ledger correctness, idempotency, rejected-transaction visibility, recovery boundaries, and the reservation lifecycle. en https://tuladb.com/blog/ledger-correctness-write-path/ https://tuladb.com/blog/ledger-correctness-write-path/ Why financial state should not be scattered across application code, queues, and reconciliation jobs. https://tuladb.com/blog/idempotency-ledger-correctness/ https://tuladb.com/blog/idempotency-ledger-correctness/ Retries are normal in distributed systems. The durable result should remain stable. https://tuladb.com/blog/rejected-transactions-are-records/ https://tuladb.com/blog/rejected-transactions-are-records/ A failed business decision can still be operational evidence. https://tuladb.com/blog/snapshots-are-recovery-boundaries/ https://tuladb.com/blog/snapshots-are-recovery-boundaries/ A snapshot is not just a speed optimization. It is a durable point of explanation. https://tuladb.com/blog/holds-are-not-failed-transfers/ https://tuladb.com/blog/holds-are-not-failed-transfers/ Why reserve, commit, and rollback deserve first-class ledger states in value exchange systems.