Demo Center

Hackathon simulations Architecture is provider-swapped when keys are added.

Mock transparency

Vision and analytics clearly labeled as mock when WOLFRAM_APP_ID / vision model not configured. Replace via lib/vision/analyzer.ts & lib/analytics/wolfram.ts — UI and DB unchanged.

Africa's Talking SMS is simulated until AT_USERNAME + AT_API_KEY are set. Notifications still persisted with status=simulated.

Demo Center

Simulate the full MONITOR → DETECT → ANALYZE → VERIFY → ACT workflow without external credentials.

Most important: Run Environmental Event executes the 8-step chain: imagery → vision → NDVI → analytics → risk → alert → investigation → SMS — shown as a timeline on the right.

Execution timeline

Visual trace of the demo pipeline

Update Plot C3 imagerypending

Run computer vision analysispending

Calculate NDVI + changepending

Run environmental analyticspending

Calculate risk scorepending

Create alertpending

Generate field investigation requestpending

Simulate SMS via Africa's Talkingpending

Run Environmental Event above — actionable cards and auditable JSON will appear here for judges to verify without opening DevTools.

What Run Environmental Event proves

Single workflow: MONITOR → DETECT → ANALYZE → VERIFY → ACT

1. MonitoringMap (Leaflet) + plots colored by health (getPlotStatus/getPlotStyle).

2. Vision mock on Plot C3 → veg 38%, canopy 34%, bare soil 52%.

3. NDVI 0.68 → 0.42 = -38.2%.

4. Risk 84 critical → alert created → field investigation.

5. SMS via provider abstraction → notifications row.

All via Next.js Route Handlers under app/api with Zod + consistent success/data/error.