Where to start. The dashboard groups every L1 SHOULD-constraint into one tab per exception kind — drift, overdraft, limit breach, expected EOD balance variance — plus a Today's Exceptions roll-up. Each tab queries one L1 invariant view directly; rows ARE the constraint violations.
L1 Reconciliation Dashboard
Sasquatch National Bank's combined treasury + merchant-acquiring view. SNB runs a Cash Management Suite (CMS) for commercial customer DDAs and ZBA cash concentration, AND a merchant-acquiring service that processes card-network sales for retail merchants and pays them out via ACH / wire / check. The L2 instance below covers both surfaces in one model — the L1 dashboard renders treasury invariants (drift, overdraft, limit breach), the L2 flow-tracing dashboard surfaces merchant-acquiring pipeline structure (XOR payout vehicles, TransferKey-grouped settlement cycles, external card-network aggregation).
L2 Coverage What this dashboard reconciles, derived from the configured L2 instance:
10 internal accounts, 6 external accounts
3 account templates (role classes that bind to specific accounts at posting time)
29 rails (reconciliation patterns the integrator declares)
3 transfer templates (multi-leg shared transfers)
5 chains (transfer-of-transfers ordered flows)
7 limit schedules (daily outbound caps by parent role × transfer type)