AG Grid & Charts

Every table and every figure in this product is drawn by AG Grid's grid or its charts, and each one of them reads rows this gateway produced — an order the server already judged, a ledger entry PayPal confirmed, a campaign that shipped with the app. This page names the widget, the screen, and the function that makes its numbers, and then carries the one card the three-minute video had no room for. The diagram was generated from this repository with Archify and is served as-is: the file you see is the artifact, not a re-drawing of it.

Generated 1 November 2026

🎬 It moves. Hover any box to watch what travels along its edges; press Live (top right of the diagram) and the flow runs on its own. A diagram that looks still is honouring your system's reduce motion setting — the toggle is disabled while that is on, which is deliberate.

Which widget renders what

Read from the components themselves, not from memory. Where a widget is not a chart library's, the row says so rather than flattering it.

WidgetScreenDrawn withFed by
AgentGrid/overviewAG GridPolicy rows — every order, with the server's verdict already applied
Money in flight/overviewAG Charts`lib/moneyInFlight` sums those same rows by state; a click opens the rows it summed
JsonGrid/activityAG GridLedger entries typed into columns by `lib/gridColumns`
Where the money went/activityits own bars — not a chart library`lib/activityByType` over the policy rows, one entry per currency
ProjectGrid/crowdfundingAG GridThe shipped campaign seed, normalised before the grid ever sees it
PortfolioDonut/crowdfundingAG ChartsPledges by state: paid, reserved, returned
FutureValue/crowdfundingAG ChartsCommitted money at the campaign's own offered rate — never a rate invented here
MarketFigures/appendices/target-marketAG ChartsThe market figures cited in the target-market appendix

Two names worth keeping apart: Money in flight lives on /overview — it is mounted inside AgentGrid — while Where the money went is the first card on /activity. Neither is the other; the video's time made only the first one visible.

Where the money went — the card the three-minute video had no room for

The submission video spends every second it has on the argument: an agent that asks to spend, a server that refuses what breaks the envelope, a human who approves inside PayPal. There was no second left for the first card on /activity, and the hackathon asks for work “sufficiently documented for the judges to understand and evaluate it” — so the card is documented here, with the function that produces its numbers.

What it answers

Adónde se fue el dinero — where the money that actually moved went, asked before the ledger asks to be read. Three books, each with its total and a bar for its size:

BookSums
Purchasesorders that settled — money that completed
Transfersmoney sent to a person
Investmentsstakes in crowdfunding campaigns

Where the number comes from

  • activityByType(readPolicyRows()) — the card sums the policy rows the browser holds, by kind.
  • One bar per currency.100 USD and 100 PYUSD are not 200 of anything, so they are never added — the axis stays honest.
  • Deliberately one colour. The palette already means things — green settled, grey returned, amber running out of room — so a second palette would teach a vocabulary the rest of the product does not speak.
  • Money held and money given back are counted in Money in flight and in the portfolio, not here twice: counting them again would report the same dollars in two stories.

The licence, stated plainly

This build runs on AG Grid's trial licence, and AG Studio — the dashboard product — is read by the config but not wired to a screen yet. In AG Grid's own hackathon briefing: “if you don't have an API key, we won't penalize you for that in the judging”. The grid and the charts here are the Community and trial features the app actually uses; nothing on any screen needs an Enterprise feature that would silently vanish without a key.