Files
Noel Sabia 1ff3bc8290
release-please / release-please (push) Failing after 3s
docs(mission): add weather and holiday context
2026-11-13 20:27:06 +01:00

11 KiB
Raw Permalink Blame History

Open decisions

Answer these in chat; I will update the docs. Each has a recommended answer and a default. If an answer is missing by Friday 22:00, we build the default.

Settled facts (no need to answer)

  • Challenge: Schwarz Digits — Pulse of the City. The repo's remaining source material and the proposed stack both point there. If this is wrong, say so now.
  • Data: downloaded and inspected. 8 usable sensors, 5 months of multi-sensor data, 15-minute cadence, 580 m inner-city cluster. See data.md.
  • Baseline: day-ahead MAE 3.36 with weather vs 5.40 seasonal naive; WAPE 27.8% vs 44.7%. Credible, not spectacular.
  • Onyx + Nuxt: @sit-onyx/nuxt 1.2.0 and @sit-onyx/chartjs-plugin 1.0.1 exist. The integration risk is lower than expected.
  • Deadline: preselection Sunday 10:00; submit by 13:00; final 14:00.
  • Repo: greenfield application; only the knowledge bundle and organizer PDFs exist. No app code to preserve.

Round 2 answers (2026-11-13)

Q Answer
Q1 Open — central discussion. See mvp.md.
Q2 SKE access requested, expected today. Namespace-only — no cluster-admin. Gitea registry at git.noelsabia.dev. Custom domain via manual Cloudflare record.
Q3 Solo, using herdr to coordinate many AI agents.
Q4 (a) + (c): live dashboard + presenter-driven what-if broadcast. No audience-as-sensors, no poll chosen.
Q5 Nuxt used often in production; no Onyx experience; likely SSR for fast first render.
Q6 Python service with batch updates + FastAPI called by Go; horizons 15 min, 1 h, 48 h, 7 d.
Q7 No auth/SSO; public multi-user; live data refresh via polling; bare-minimum CI/CD and observability; HTTPS and health checks required.
Q8 120 people will connect; design for that.
Q9 Win = fully deployed on STACKIT, usable on every phone, reusable for later use cases, and a published technical paper.
Q10 User handles submission logistics.

New fact: Nuxt 4.6.4 + Onyx 1.22.0 SSR was smoke-tested tonight: build and server render work (HTTP 200, Onyx button in server HTML). SSR is viable.

Round 3 answers (2026-11-13, later)

Q Answer
Q1 Staffing copilot + SSE. Q1 is settled.
Q1.1 Lidl/Kaufland store manager.
Q1.2 A usable next-week shift plan, generated in a few seconds. Not a research optimizer.
Q1.3 Forecast + scenario engine is the reusable core.
Q2 SSR is fine.
Q3 SSE for live scenario; frontend polls for data/model updates.
Q4 The paper is a hackathon deliverable.
Q5 Four workstreams, four worktrees, one contract.
Q6 Kubeconfig provided; namespace-only verified. See below.
Q7 Basic auth is acceptable. Scope to confirm: /control only, or the whole app.
Q8 k6 for load testing.
Q9 AI may write the paper; needs a technical checklist and human verification.

Verified from the provided kubeconfig

  • Context fch26-onemanarmy-sa-context, namespace fch26-onemanarmy.
  • Service account token valid until 2026-11-23 19:49 CET — enough for the hackathon.
  • Can create: Deployments, Services, ConfigMaps, Secrets, ServiceAccounts, Pods, PVCs.
  • Cannot create: Ingress, Jobs, CronJobs, NetworkPolicies, Roles, RoleBindings.
  • No cert-manager CRDs, no Gateway API, no IngressClass visibility.
  • No ResourceQuota or LimitRange — three small pods fit.
  • Public image pull works; a non-root nginx-unprivileged pod ran successfully.
  • Exposure path: Cloudflare Tunnel, not Ingress.
  • Batch path: build-time, not a Kubernetes Job/CronJob.
  • Security: the kubeconfig is a secret, now git-ignored and chmod 600. Rotate the token after the event; it was shared in chat.

Weather/holiday scope — resolved: use Open-Meteo (historical archive for training; current/7-day forecast for the dashboard) and German/Baden-Württemberg public holidays 2025–2026. The ML service uses the same context as features. The earlier "only what is available" is read as "no invented data"; public context is in. See data.md.


Q1 — Hero use case

Question: Which use case is the product? (a) dynamic staffing, (b) targeted advertising, (c) strategic store locations, (d) city operations, (e) all three.

Why it matters: "All three" is how you end up with a generic dashboard, which the preselection criteria explicitly penalize. The data supports staffing best: 8 locations, 5 months, clear daily/weekly peaks. Store-location ranking needs city-wide granularity we do not have.

Recommendation: (a) dynamic staffing for one inner-city store. The map and advertising view are supporting evidence, not the product. Store location is a vision slide only.

Default: staffing.


Q2 — SKE access and domain

Answered: Access verified. Namespace fch26-onemanarmy; service account can create workloads but not Ingress, Jobs or CronJobs. No cert-manager, no external-dns, no quota. Use Cloudflare Tunnel for pulse.noelsabia.dev and api.pulse.noelsabia.dev, and the Gitea registry with an imagePullSecret. See architecture.md and friday-blockers.md.


Q3 — Team, time, and agents

Question: Are you solo with AI agents, or are there human teammates? How many humans, what are their strengths (frontend, ML, infra, design, pitching), and how many productive hours can each give? How many agents can run in parallel, with what tooling? How much sleep are you planning?

Why it matters: The human is the integration bottleneck. More agents do not remove the need to review, merge, deploy, and rehearse. A 24-hour all-nighter costs you the 30% storytelling score.

Recommendation: 1 human + 3–4 agents maximum, each with a folder and a written contract. Sleep 4–5 hours. Feature freeze Saturday 23:00. If solo, cut the audience view, the poll, the custom domain, and the battery panel.

Default: solo + agents; 4 hours sleep; cut P1.


Q4 — What "realtime on phones" means

Question: Which of these do you mean? (a) the dashboard updates live, (b) the jury's phones act as sensors, (c) the presenter changes a what-if scenario and every phone updates, (d) the audience votes/polls and the big screen reacts.

Why it matters: (b) is a privacy and reliability trap; it is also not the challenge. (c) is the strongest demo: it makes the jury feel the decision. (d) is a nice engagement layer but another moving part.

Recommendation: (c) + (a), with (d) as optional P1. Never (b). The live layer must deliver the core value — a changed staffing recommendation — not just moving numbers.

Default: (c) + (a); (d) if time.


Q5 — Frontend stack

Question: Nuxt + Onyx, Nuxt + custom UI, or plain Vue + Vite + Onyx? Have you used Nuxt and Onyx before? Do you want SSR or a static SPA? MapLibre or a static basemap?

Why it matters: The bonus says Vue.js, not Nuxt. Nuxt adds build complexity; Onyx has an official Nuxt module, so it is less risky than it looks. A live map adds a tile/network dependency; a static basemap is more reliable on stage.

Recommendation: Nuxt 4 SPA (ssr: false) + @sit-onyx/nuxt + Chart.js/Onyx if you are comfortable with Nuxt. Otherwise plain Vue + Vite + Onyx. Use MapLibre for the demo, with a static basemap fallback. Do not bet the UI on a component library you have never used.

Default: Nuxt SPA + Onyx; static basemap fallback.


Q6 — ML shape

Question: Python batch training with precomputed forecasts, a Python FastAPI inference service, or a Go-only heuristic? What horizon and granularity: 7 days hourly, 48 hours 15-minute, or both? Retrain at runtime?

Why it matters: A Python service is a third runtime to deploy, monitor, and debug. The model is small and the data is static; batch is more production-sane and more reliable on stage. The what-if scenarios can be precomputed as a grid.

Recommendation: Python batch, global HistGB, 7-day hourly forecast, weather-aware, with a precomputed scenario grid. No runtime Python. Show metrics and a seasonal-naive baseline. If the jury asks for live inference, explain the trade-off; do not add it at 20:00.

Default: batch.


Q7 — "Production-ready" bar

Question: What must production-ready include for you? Auth/SSO? Multi-user? Live data refresh? HA? CI/CD? Observability? Or is it "deployed, HTTPS, health checks, seeded data, docs"?

Why it matters: "Production-ready" is unbounded. In 24 hours, auth and HA would eat the demo. The judges reward understanding and reliability, not a checklist of enterprise features you cannot finish.

Recommendation: SKE + HTTPS + health/ready + resource limits + seeded data + README + architecture diagram + no secrets + honest limitations. No auth for the public dashboard; a token for /control; one replica, documented. Say what is not production-ready.

Default: as recommended.


Q8 — Demo environment

Question: Are you on site? How many people in the room? How reliable is the Wi-Fi? Is there a projector? Are QR codes allowed? Will phones use mobile data? How much travel/setup time before 10:00?

Why it matters: The demo is a judged implementation criterion. A live audience view that depends on venue Wi-Fi is a single point of failure.

Recommendation: Design for 50–100 phones on mobile data, one presenter, one driver, a recorded 90-second fallback, and a printed QR code. Test the QR on site. The app must work without the audience view.

Default: 50 phones, mobile data, backup video.


Q9 — Success definition

Question: What does winning look like: advancing from the Schwarz Digits preselection, winning the final, building a reusable product, or learning something specific?

Why it matters: Preselection and final reward different things. Preselection is the gate; the final weights vision and storytelling. A reusable product would need more docs and less demo polish.

Recommendation: Win the Schwarz Digits preselection; treat the final as a stretch. Optimize every decision for the Sunday 10:00 demo, not the 14:00 stage.

Default: preselection.


Q10 — Submission and logistics (lower priority)

Question: Where and how do we submit the presentation and code by 13:00? Is there a template or portal? Is the repo expected on GitHub? Do we need a PDF, a link, or both? What time do you need to leave for the venue?

Why it matters: A last-hour submission surprise is avoidable. This does not change the build, but it changes the Sunday checklist.

Recommendation: Confirm with the organizers today. Prepare a PDF deck, a public repo, and the live URL. Submit by 12:30, not 13:00. Pack a USB stick and a charger.

Default: PDF + repo + live URL; submit 12:30.


Answer template

Copy this into chat:

Q1: staffing / advertising / store location / city / all
Q2: access status, registry, DNS zone, domain, mentor contact
Q3: humans, agent count/tooling, hours, sleep
Q4: a / b / c / d (can combine)
Q5: Nuxt / Vue / SSR / SPA / map choice, experience level
Q6: batch / FastAPI / Go, horizon, granularity
Q7: must-have list
Q8: on-site, audience size, Wi-Fi, projector, QR, mobile data
Q9: preselection / final / product / learning
Q10: submission mechanism, travel time