Build interactive risk dashboard for exhibition demo

Specifications for MVP 1. Purpose An interactive risk dashboard to demo at an exhibition as the MVP. It should look polished, run reliably at the booth while offline, and let visitors click around and watch risk indicators change. 2. Objective and Requirements Build a single-page, interactive dashboard that displays 3 risk indicators across 3 countries with a live-feeling interactive element so booth visitors can explore and see values update in real time. This is a marketing demo and lead-generation tool. The dashboard must run fully offline from a laptop at the booth, with no dependency on venue wifi. All data, map geometry, and assets are bundled locally. 3. Out of Scope • No user accounts, login, or backend/database. • No real automated data pipeline or rules engine. MGC will supply indicator values as static data. • No mobile app. Desktop/large-display only. • Not the eventual SaaS product; this is meant to be a preview. 4. Interactive and simulated "live" element A "scenario" or time slider, or a play button, that steps through 2 to 4 predefined states and animates the map recoloring and risk escalation pathways (e.g., "baseline" to "trigger event", for example). Fully offline, high visual impact, to showcase the risk escalation pathways for selected countries. 5. Tech Stack • Frontend: Plain HTML/CSS/JavaScript, or lightweight React via Vite (developer's choice; vanilla is preferred for simplicity and offline robustness). • Map: MapLibre GL JS or Leaflet (both free, open-source, no API key). Render local GeoJSON admin boundaries (source: GADM or Natural Earth) so there are no paid map tiles and it works offline. A plain background with colored region polygons (no basemap tiles) is acceptable and maximizes reliability. • Charts / gauges: Chart.js (vanilla) or Recharts (if React). • Data: Static JSON files bundled with the app. JSON file provided by us. No backend. • Animation/state: Native JS and CSS transitions, or minimal state handling. • Build & version control: Vite build; private GitHub repository. • Deployment: Static host free tier (Cloudflare Pages, Netlify, or Vercel) as backup URL, plus a locally runnable build on the booth laptop as the primary. 6. Budget and Terms • Budget: TBD • Timeline: 2 months (September – October, handover by end October) with milestones. • NDA and IP-assignment clause required. Developer must not reuse our risk framework and related technical assets, data, branding, or design.