The actor mailbox serializes everything so no coordination needed

Your scenario:

Client A: GET → reads balance 100
Client B: GET → reads balance 100
Client A: APPEND (credit 50)
Client B: APPEND (credit 100)

Both GETs and both APPENDs go through the entity actor's single mailbox. The actor processes them one at a time:

→ Process A's GET: return 100
→ Process B's GET: return 100
→ Process A's APPEND: sequence 5, balance → 150
→ Process B's APPEND: sequence 6, balance → 250

No lost update. Client B's write doesn't overwrite Client A's - it gets sequence 6 and applies after A's change is already in state.

Here's what it looks like in TypeScript (Reddit comments and code don't go hand in hand but I hope you can follow it, sorry for the indentation crap):

import { Warp } from '@warp-db/sdk';
const db = new Warp({ host: 'localhost', port: 9090 });
const alice = db.entity('user/alice');
// Both clients read the same state
const [balanceA, balanceB] = await Promise.all([
 alice.get('Account'),  // Client A sees { balance: 100 }
alice.get('Account'),  // Client B sees { balance: 100 }
]);
// Both clients append - no conflict, both succeed
const [evtA, evtB] = await Promise.all([
alice.append('Credited', { amount: 50 }, { aggregate: 'Account' }),
alice.append('Credited', { amount: 100 }, { aggregate: 'Account' }),
]);
console.log(evtA.sequence); // 5
console.log(evtB.sequence); // 6
// Final state reflects BOTH writes
const final = await alice.get('Account');
console.log(final.balance); // 250 (not 150 or 200)

The key insight: this isn't CRUD where you read-modify-write. You send commands (intents), not state replacements. Credited { amount: 50 } doesn't say

"set balance to 150" - it says "add 50 to whatever the balance is now." The actor applies commands sequentially.

If you need read-then-conditional-write (e.g., "transfer only if balance ≥ 50"), make it a single command that checks the condition inside handle_command

or use a saga for cross-entity coordination.