docs(mission): add weather and holiday context
release-please / release-please (push) Failing after 3s

This commit is contained in:
Noel Sabia committed 2026-11-13 20:27:06 +01:00
1 parent 8afb767585
commit 1ff3bc8290
8 files changed
+109 -25

No files matched your search

+8 -3
View File
@@ -22,8 +22,8 @@ Rehearse the 5-minute version first. The 8-minute version is the same story with
|---:|---|---|
| 0:00–0:30 | Hook | "It's Friday. A store manager on Kaiserstraße has 12 staff and a sunny Saturday forecast. Should she schedule 8 people or 14? Today she guesses. We built the answer." |
| 0:30–1:15 | Problem | Raw counts are not decisions. Weather, events, and time of day change the crowd. A generic dashboard shows history; it does not tell her what to do. |
| 1:15–4:15 | **Demo** | Phone: pick Stadtgalerie. Week view: Saturday peak. Staffing plan: recommended shifts, coverage, cost. Change scenario: sunny Saturday + Christmas market. Forecast rises; plan changes. The jury's phones update. |
| 4:15–5:15 | How it works | 8 sensors, 15-minute data, 5 months. Weather fusion. Global model; time-based validation; MAE 3.36 vs 5.40 seasonal naive; WAPE 27.8%. Go + Nuxt + Onyx on SKE. No PII. |
| 1:15–4:15 | **Demo** | Phone: pick Stadtgalerie. The dashboard shows the latest Heilbronn weather and German holiday badges. Week view: Saturday peak. Staffing plan: recommended shifts, coverage, cost. Change scenario: sunny Saturday + Christmas market. Forecast rises; plan changes. The jury's phones update. |
| 4:15–5:15 | How it works | 8 sensors, 15-minute data, 5 months. Weather + holiday context. Global model; time-based validation; MAE 3.36 vs 5.40 seasonal naive; WAPE 27.8%. Go + Nuxt + Onyx on SKE. No PII. |
| 5:15–6:00 | Honest limits | 8 sensors, 580 m, 5 months, devices not people, observed weather not forecast, no event log. What we would do with more data. |
| 6:00–7:30 | Vision | Add POS data, event calendars, forecast weather, more sensors. Multi-store staffing API. City operations view. Start with one store, one decision. |
| 7:30–8:00 | Close | "PulseCast: from footfall to shifts. The demo is live at `<URL>` — open it now." |
@@ -86,7 +86,10 @@ Never debug on stage. If the app is down, switch to the video and keep the story
> Time-based holdout: train June–October, test the last 28 days. Day-ahead MAE 3.36 with weather vs 4.20 without vs 5.40 seasonal naive. WAPE 27.8% vs 44.7%. We show the baseline and the limitations in the app.
**"Is the weather real or synthetic?"**
> Historical observed weather for training and validation. The what-if scenarios are counterfactual inputs to the model, clearly labeled as scenarios. In production we would use the forecast API and show a confidence band.
> Historical observed weather from Open-Meteo for training and validation. The dashboard shows the latest Heilbronn weather and a 7-day forecast; the what-if scenarios are counterfactual inputs to the model, clearly labeled as scenarios. The forecast still renders if Open-Meteo is down because Go caches the last context payload.
**"What about holidays?"**
> The dashboard shows German/Baden-Württemberg public holidays from the past and uses an `is_holiday` feature. Weather is the main accuracy driver; the holiday feature added little in our 28-day test, so we present it as context, not a miracle. That honesty is part of the product.
**"Why Nuxt + Go + Onyx?"**
> Vue and Go are the Digits stack; Onyx is the design system. Nuxt gives us a fast, typed frontend build; Go gives us one small binary with SSE and static serving. One deployable, fewer failure modes. The Onyx Nuxt module is official.
@@ -114,6 +117,8 @@ Never debug on stage. If the app is down, switch to the video and keep the story
- "Production-grade" without the caveat.
- "AI" as a feature. The model is a means to a decision.
- "We built a platform." You built a product for one decision.
- "Holidays improve accuracy a lot." They are context; weather is the main driver.
- "Live weather data." It is the latest forecast/current conditions plus historical weather, not a live sensor feed.
## Slides (max 8)