Banking System

Ownership and transitions

A successful transfer commits both balances, the outgoing total, and the replay record as one transition. Store its original returned balances; recomputing a retry from later live balances breaks idempotency. Failed requests reserve no ID, and a conflicting accepted ID must not overwrite its replay record. Point operations are expected O(1); ranking all accounts costs O(A log A), and retained replay entries consume O(requests).

JavaScript boundaries

Use native classes with per-instance state and plain object/array snapshots. Object assignment shares a reference; copy retained inputs and every outward mutable container, including nested arrays. null means absence. Map handles arbitrary string keys safely, including "__proto__"; do not confuse a missing key with zero or an empty string. Domain validation uses RangeError. Numeric inputs must satisfy Number.isSafeInteger, so booleans, fractions, infinities, and NaN are invalid where an integer is required. All documented aggregate results and timestamp-plus-duration sums fit the safe-integer range. Strings use exact case-sensitive equality; lexical order compares JavaScript UTF-16 code units. Calls are serialized and synchronous.

const internal = ["initial"];
const snapshot = [...internal];
snapshot.length = 0;
console.assert(internal.length === 1);

A detached snapshot protects ownership; the service still has to validate and commit a coherent transition.