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

+6 -4
View File
@@ -54,14 +54,16 @@ The technical stack is not the differentiator. Nuxt SSR, Go, FastAPI, SSE and SK
## The MVP in five screens
1. **Now** — pulse map of the 8 sensors, current/replay reading, weather, last update. This is the "Pulse of the City" context.
2. **Forecast** — 48-hour and 7-day forecast per location, with uncertainty band, weather context and baseline comparison.
3. **Plan** — the hero screen: recommended staff per hour, shift blocks, coverage score, over/understaffed hours, estimated labor cost, comparison to a flat schedule.
1. **Now** — pulse map of the 8 sensors, current/replay reading, **latest Heilbronn weather**, **German/Baden-Württemberg holiday badge**, last update. This is the "Pulse of the City" context.
2. **Forecast** — 48-hour and 7-day forecast per location, with uncertainty band, **weather strip**, **holiday markers** and baseline comparison.
3. **Plan** — the hero screen: recommended staff per hour, shift blocks, coverage score, over/understaffed hours, estimated labor cost, comparison to a flat schedule, and a **"why this plan" context card** that names the weather/holiday driver.
4. **Simulate** — presenter changes weather / event / service standard; forecast and plan update; all phones stay in sync via SSE.
5. **About** — data coverage, model metrics, assumptions, privacy, limitations.
5. **About** — data coverage, weather/holiday sources, model metrics, assumptions, privacy, limitations.
The hero screen is **Plan**. Everything else supports it.
**Context layer:** the dashboard shows the latest weather and historical German holidays, and the Python ML microservice uses the same context as features. This is not decoration: weather is the main accuracy driver, and holidays explain spikes. It makes the product feel like it understands the city, not just the sensor.
**Plan generation requirement:** one click on "Generate next week" returns a shift plan in **under 2 seconds**. The plan is a table of 2–4 hour shift blocks per day, staff counts per hour, coverage score, cost, and a comparison to a flat schedule. The manager can edit the assumptions and regenerate. Export as CSV/print view. Not a drag-and-drop optimizer; a usable plan, fast.
## The decision logic — transparent, not magic