docs(mission): add weather and holiday context
release-please / release-please (push) Failing after 3s
release-please / release-please (push) Failing after 3s
This commit is contained in:
1 parent
8afb767585
commit
1ff3bc8290
8 files changed
+109
-25
No files matched your search
@@ -13,6 +13,7 @@ Most teams will ship a footfall dashboard. **We ship a staffing copilot**: a sto
|
||||
Why this bet:
|
||||
|
||||
- **The data supports it.** 8 sensors, 5 months of multi-sensor data, 15-minute intervals, clear daily and weekly peaks. See [data.md](data.md).
|
||||
- **The context makes it credible.** The dashboard shows the latest Heilbronn weather and German/Baden-Württemberg holidays; the Python ML service uses the same context as features. Weather is the main accuracy driver.
|
||||
- **The challenge supports it.** "Dynamic Staffing" is one of the three named use cases; predictions are the explicit stretch goal.
|
||||
- **The judging supports it.** Originality is a stated criterion and "generic dashboard" is the thing to avoid. A decision workflow is distinctive.
|
||||
- **The demo supports it.** One scenario change visibly changes a recommendation on every phone.
|
||||
@@ -39,6 +40,7 @@ Why this bet:
|
||||
- Deployed on SKE, public HTTPS URL, health checks, README.
|
||||
- 8-sensor map with measured points (no fake city-wide heatmap).
|
||||
- 7-day hourly forecast per sensor, weather-aware, validated against a baseline.
|
||||
- Latest weather and German/Baden-Württemberg holiday context in the dashboard, used by the ML service.
|
||||
- Staffing recommendation view with transparent assumptions.
|
||||
- Live scenario broadcast (SSE) to stage + phones.
|
||||
- Mobile-responsive; works on a phone without installing anything.
|
||||
|
||||
Reference in new issue
Block a user