# Mission — PulseCast **Status: DRAFT.** The product choice below is a recommendation, not a settled decision. Open decisions are in [questions.md](questions.md). Do not treat this as final until Q1 is answered. ## The task, in one paragraph Schwarz Digits' **Pulse of the City** challenge asks for a production-ready application on STACKIT/SKE that turns privacy-preserving PAX-counter footfall data from Heilbronn's inner city into decisions about advertising, store locations, or staffing. Bonus points for **Vue.js + Go + Onyx**. Judged on idea, implementation, reliability, documentation, and storytelling. We have from **Saturday 07:00** to **Sunday 13:00**; the preselection demo is **Sunday 10:00**. ## The bet Most teams will ship a footfall dashboard. **We ship a staffing copilot**: a store manager sees the next 7 days of footfall, gets a shift recommendation, and can test weather/event scenarios live. The map and charts support the decision; they are not the product. 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. ## Hero user and decision - **User:** store manager at an inner-city retailer (e.g. near Stadtgalerie / Kaiserstraße). - **Decision:** "How many staff per hour next week, and when?" - **Output:** 7-day hourly forecast, recommended shift plan, coverage/cost, what-if scenarios. - **Secondary:** city operations / PreZero can use the same pulse map. They are not the hero. ## The 3-minute demo 1. Open on a phone. Pick "Stadtgalerie." 2. See the week: Saturday peak, weather context, recommended shifts. 3. Change scenario: **"sunny Saturday + Christmas market."** Forecast rises; recommendation adds staff; cost/coverage updates. 4. The same change lands on the jury's phones via the live view. *"You just saw the decision a manager would make."* 5. Close on the honest limitation: 8 sensors, 5 months, estimates not counts — and the path to more. ## Scope **Must (P0):** - 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. **Should (P1):** - Audience "join the pulse" QR view + poll. - Onyx components; Chart.js with the Onyx theme. - Sensor health/battery view; data-coverage panel. - Custom domain via Cloudflare Tunnel. **Cut (P2):** - Store-location recommender; city-wide heatmap claims. - Live Python inference service; deep learning; LLM chat. - Auth/SSO/multi-tenant; Postgres/Kafka/Flink; CI/CD beyond a Makefile. - Real-time sensor ingestion — we only have a CSV. - Custom domain if it blocks deployment. ## Definition of done - A judge can open the URL on a phone, pick a store, see next week, change a scenario, and see a recommendation change in under 2 seconds. - The app survives a cold start, a refresh, and 120 concurrent SSE clients. - The README explains what it does, how it works, how to run/deploy it, and where it breaks. - The demo can run from a laptop + 3 phones, with a recorded fallback. - No PII, no MAC addresses, no fake precision. ## Success - **Primary:** win the Schwarz Digits preselection on Sunday 10:00. - **Stretch:** final pitch at 14:00. - **Evidence:** deployed URL, reliable demo, clear decision, honest limitations, documentation. ## Non-negotiables - No coding after **Sunday 06:00**. No cluster changes after **Sunday 06:00**. - No demo dependency on venue Wi-Fi: phones use mobile data; the laptop has a local fallback. - No generic dashboard. Every screen answers "what should I do?" - No claim that 8 sensors measure the whole city. ## Folder map | File | Purpose | |---|---| | [README.md](README.md) | Mission, product thesis, scope, definition of done. | | [data.md](data.md) | What the actual PAX data contains, what it supports, and the baseline model results. | | [architecture.md](architecture.md) | Smallest architecture that survives the stage, deployment plan, failure modes. | | [plan.md](plan.md) | 24-hour timeline, gates, agent workstreams, risks. | | [demo.md](demo.md) | Pitch script, live demo choreography, fallback ladder, Q&A bank. | | [questions.md](questions.md) | Open decisions with recommendations; answer these first. |