Every frame below is a live Mosofin artifact—not a mockup. Each one is regenerated from versioned JSON IR, checked for structural integrity, and linked to the exact source that produced it.
Every scenario has named reader views with a path-aware Story Trail, shareable navigation, dark/light rendering, self-contained export, and a machine-readable quality receipt.
The whole business in one map: demand, supply chain, inventory, commerce, payments, spend, payroll, bank and three separate ledgers, each node naming its system of record.
Shopify → Stripe → Chase 1002 → QuickBooks with one source of truth per fact, the wholesale A/R loop, and no invented amounts.
Checkout, card capture, the T+2 net payout, and the three facts QuickBooks matches: sales receipt, fee, and deposit.
Gross Shopify sales to the QuickBooks revenue line: contra items, pass-through tax and gift cards, and fees kept below revenue.
Lanes by system, a zero-difference reconciliation gate owned by the controller, and a break lane that blocks the period lock.
Refund, Stripe reversal, payout netting, and the QuickBooks entry — with chargeback waits, terminal losses, and a recoverable books miss.
Gross charges less refunds less fees per payout, in-transit timing, wholesale ACH explained separately, and a residual that must be zero.
DTC checkout is a sales receipt with no receivable; only QuickBooks invoices create A/R, and the aging report is the only list of who owes.
A tied Chase opening balance, only named inflows, dated outflows to 15 August, and an answer that is unknown rather than guessed.
Share the redacted source, verified artifact, validation receipt, and visual-review result. Approved work can join the community Proof Lab with attribution.
$ node scripts/build-gallery.mjs
render workflow ✓
render sequence ✓
render dataflow ✓
render lifecycle ✓
render architecture ✓
receipt 81 checks / 9 artifacts / deterministic hashes