scroll ↓ or press play

MetricManager: A Live Theme Park Dashboard

November 2026

MetricManager is a proof of concept for governing business metrics: where every number comes from, who owns it, what changed it, and whether it can still be trusted. To test it, it needs data whose real story is known. So it simulates five years (2022–2026) at Tidewater Park, a fictional seaside amusement park, and keeps two separate records of each day: what actually happened, and what the park's systems recorded. Turnstile sensors degrade, a POS terminal drops batches, a survey vendor changes, and a heatwave and a new coaster cause real shifts that look a lot like measurement failures. The monitors only ever see the recorded side, and are graded against the true one.

The dashboard below is live. Your browser downloads Python (about 30 MB the first time, then cached), simulates the park's first 60 days, and then adds a new day about every four seconds, recomputing every metric and re-running every check as it goes. Nothing runs on a server, so you get your own park: change its decisions or break it as much as you like.

Open the dashboard full screen →

Things to try

How it's built

The full project runs locally as a full-stack application: a simulator writes raw sensor, ticketing, ride and point-of-sale feeds; eleven staging tables narrow them; and 31 small metric scripts, owned by five teams, form a dependency graph. Every change to a metric script passes an automated review before it can merge. Lineage is published as OpenLineage events and an Apache Ossie semantic model, and SQLite databases and an HTTP server feed the live dashboard.

The version on this page is a lighter child of that project. It reuses the same simulator, metric scripts, monitors, health checks and dashboard, running in your browser on Pyodide (Python compiled to WebAssembly) inside a background worker. The databases, server, lineage publishing and review gate stay in the local version; here the park lives in the page's memory, keeps the most recent 400 days, and starts over when you reload.

On a desktop browser a simulated day takes about two seconds of work, so older laptops and phones may fall a little behind the four-second day.