Skip to content

Milestones

List view

  • v0.8 — Integrations

    Goal: connect to the ecosystem. MultiGP RaceSync (roster import, queued/resumable results push); credential handling. Open-data API + export + embeddable widgets — the cross-event surface leans on the Cloud warehouse from v0.7. Done when: roster import + results push work against a chapter, and the open-data API + widgets serve. Ref: docs/roadmap.html §2 · docs/integrations.html

    No due date
    •0/2 issues closed
    0% complete2 open0 closed

  • v0.7 — Cloud

    Goal: off-LAN reach and longevity. One-way resumable push (Director → Cloud); Postgres warehouse via the same server crate + storage trait. Accounts + free-account-gated reads; the live relay (same PWA off-LAN) + web push; long-term portal basics (career, standings); the season model. Done when: a Director with internet relays a live event to off-LAN viewers, a season aggregates across events, and a self-hosted Cloud deploy is documented. Ref: docs/roadmap.html §2 · docs/cloud.html

    No due date
    •0/3 issues closed
    0% complete3 open0 closed

  • v0.6 — Streaming / broadcast

    Goal: stream a race — overlays and OBS direction — entirely on the LAN, no Cloud required. OBS overlays (leaderboard, staging, podium, bracket) as read-only protocol clients, with theming. Broadcast control — obs-websocket scene maps driven by race-state, with automatic / armed / manual transition modes; the control-only capture boundary (OBS owns video). Done when: overlays render in OBS from live state and scene switches follow the heat loop — all driven by a Director on the LAN with no Cloud. Ref: docs/roadmap.html §2 · docs/streaming.html · docs/clients.html

    No due date
    •0/1 issues closed
    0% complete1 open0 closed

  • v0.5 — Racer/spectator PWA

    Goal: racers and spectators can follow along on their phones. The racer/spectator PWA (snapshot+subscribe, scoped views, LAN-degraded, install/offline where the secure context allows); QR/join-token onboarding. Done when: racers on the LAN see their next heat and live standings on their phones. Ref: docs/roadmap.html §2 · docs/clients.html

    No due date
    •0/3 issues closed
    0% complete3 open0 closed

  • v0.4 — Direct a single race (RD console, vertical slices)

    Reframed 2026-06-20 after a hands-on UI review: the protocol/server/engine/console FOUNDATION is built (#40–#56 + the contract suite/harness), but the WORKFLOW was never built through. Pivoting to vertical slices — each feature built backend → API → UI until it genuinely works — centered on the missing backbone: the **Event** aggregate (you are always inside an event; an event owns timers, pilots, heats, format, results). Foundation-first design.

    No due date
    •12/53 issues closed
    22% complete41 open12 closed