Files
OKF_Vault/mission/demo.md
T
2026-11-13 20:14:32 +01:00

7.5 KiB
Raw Blame History

Demo and pitch

The one-sentence story

"A store manager knows the weather forecast and the staff roster. She does not know how many people will walk past next Saturday. We turn five months of anonymized footfall into next week's shift plan — and you can change the scenario on your own phone."

Preselection vs final

Preselection (Sun 10:00) Final (Sun 14:00)
Audience Schwarz Digits challenge provider Broader jury
Goal Advance Win
Focus Decision, working demo, understanding Story, vision, implementation
Length Assume 5 min + questions (confirm with the organizer) 8 min pitch + 8 min Q&A
Demo Live, 3 screens Same demo, tighter

Rehearse the 5-minute version first. The 8-minute version is the same story with more context and vision.

8-minute pitch structure

Time Slide / beat What you say
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.
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."

Demo choreography

Cast: presenter (story), driver (clicks), timekeeper, fallback (video).

Devices: presenter phone, backup phone, laptop, big screen. QR code on the slide and on a printed card.

Before the demo:

  • Reset scenario to base; verify the URL on mobile data.
  • Warm the page; open the three tabs: /, /live, /stage.
  • Disable notifications, auto-updates, and sleep.
  • Charge all devices; bring a power bank and a hotspot.
  • Download the backup video to the laptop and phone.
  • Print the QR code; test it with a phone camera.
  • Confirm the projector resolution and browser zoom.

During the demo:

  1. Start on the phone, not the laptop. "This is what the manager sees."
  2. Narrate the decision, not the UI: "Saturday at 19:00 is the peak. The plan adds two people from 16:00."
  3. One scenario change only. "Let's make Saturday sunny and add the Christmas market." Pause. "Watch the recommendation."
  4. Look up at the audience. "If you open <URL>/live, you see the same change. You are the manager now."
  5. Stop on the recommendation screen. Do not scroll. Do not open a new feature.

After the demo: leave the app on /stage with the recommendation visible during Q&A.

The jury-phones moment

Purpose: make the jury feel the decision, not just see a chart. It is a storytelling device, not a data source.

What they see: a mobile page with the same scenario, the forecast delta, and a one-tap poll: "Would you add staff?" The big screen shows the room's split vs the model's recommendation.

What it is not: geolocation tracking, MAC sniffing, or a fake sensor. Say that explicitly if asked.

Fallback: if the venue network or QR flow fails, skip it and say: "The live view is optional; the decision is the product." Do not debug it on stage.

Fallback ladder

  1. Live app on the jury's phones.
  2. Live app on the presenter's phone.
  3. Live app on the laptop, projected.
  4. Recorded 90-second video.
  5. Screenshots in the deck.

Never debug on stage. If the app is down, switch to the video and keep the story.

Q&A bank

"What is the unit? Is it people?"

It is an index of estimated devices detected by PAX counters, not a census. We do not know device penetration, so we show it as an estimate and expose the assumption. The decision layer works on relative peaks, which are robust even if the absolute count is uncertain.

"Why only 8 sensors? Is this city-wide?"

No. Eight sensors in a 580 m inner-city cluster. That is exactly why we picked staffing for one store, not a city-wide heatmap or a store-location recommender. We would rather be honest and useful than impressive and wrong.

"How do you validate the model?"

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.

"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.

"Is this production-ready?"

For a hackathon: deployed on SKE, HTTPS, health checks, resource limits, seeded data, no secrets in the repo, documented limitations. Not production-ready for multi-tenant auth, HA, or live ingestion — and we say so.

"Why not store locations or advertising?"

The data supports staffing: 8 locations, 5 months, clear daily/weekly peaks. Store-location ranking needs city-wide granularity we do not have. Advertising is a secondary view; staffing is the decision with a measurable cost and schedule.

"What would you do with more time/data?"

Add POS conversion data, event calendars, forecast weather, more sensors, and multi-store optimization. Then the same engine becomes a staffing API for a retail group.

"How did you use AI agents?"

Agents owned isolated workstreams — data/ML, Go API, Nuxt UI, infra — against a written API contract. The human owned decisions, integration, deployment, and the demo. Same as a small engineering team, with faster iteration and more review.

"What broke?"

Be specific and honest: a data gap, a timezone bug, an SSE buffering issue, a model leakage mistake. Judges reward understanding more than a perfect story.

Do not say

  • "City-wide heatmap." It is 8 sensors in 580 m.
  • "Real-time sensor data." It is a historical CSV, with a live scenario layer.
  • "Predicts people." It estimates devices.
  • "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.

Slides (max 8)

  1. Title + one-line promise + URL/QR.
  2. The decision: "8 or 14 staff on Saturday?"
  3. The data reality: 8 sensors, 5 months, 15 min, 580 m.
  4. Demo (live; one slide as backup).
  5. How it works: pipeline, model, weather, metrics.
  6. The product: forecast → staffing plan → scenario.
  7. Honest limits + what we would do next.
  8. Vision + close + URL/QR.

Keep text large. One idea per slide. The demo is the slide.