LEDGER·PY running every change is one immutable event in an ordered log
Transfer saga · durable, step by step (Temporal)

Run a transfer to watch the saga hold, post, and settle — each step appends its event to the log on the left.

Concurrency · double-spend test

Fund a source for exactly one payment, then fire two transfers at the same instant. Optimistic concurrency on the event log lets one settle and rejects the other for insufficient funds — the source is debited once, never twice.

Accounts · available vs held

Balances appear once you seed accounts.

Read side · tails the same log
log head#0
events seen0

Balances are a projection rebuilt from the log; the outbox relay tails the same positions to publish events downstream. Both derive from the one ordered source of truth on the left.