What this dashboard is. The L1 dashboard answers 'are my postings internally consistent?' One step up: the L2 Flow Tracing dashboard answers 'is my L2 declaration alive?' — every Rail, every Chain, every TransferTemplate, every LimitSchedule the L2 instance declares should produce activity in the runtime data. When it doesn't, that's an L2 hygiene problem, not an L1 ledger problem.
L2 Flow Tracing
What this dashboard is. The L1 dashboard answers 'are my postings internally consistent?' One step up: the L2 Flow Tracing dashboard answers 'is my L2 declaration alive?' — every Rail, every Chain, every TransferTemplate, every LimitSchedule the L2 instance declares should produce activity in the runtime data. When it doesn't, that's an L2 hygiene problem, not an L1 ledger problem.
L2 Instance 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).