Skip to content
Rymflux Documentation
Esc
↑↓navigate↵open⌘Jpreview
On this page

v1 roadmap — themes and phases

Forward view for Rymflux v1: how the charter scope is sequenced into phases, and which backlog items (M/S/C/W) and FR/NFR refs each phase delivers.

v1 roadmap — themes and phases

This is the forward view for the v1 release. It sequences the charter scope into phases, aligned to the phase-gate cadence in the backlog. The backlog is the canonical snapshot of item status; this page is the direction — what each phase is for, what it delivers, and how we know it is done.

A public-facing version lives at ../../user/roadmap.md.

Themes

Each theme maps to a section of the charter scope and is delivered by a set of backlog items.

Theme Charter § Backlog items Key FR / NFR
Plugin system §1 Plugin system M1–M7, M15, M16 FR-PLUGIN-1..6, FR-REF-1; NFR-SEC-1..3, NFR-MAINT-2
Core platform services §3 Core platform services M8–M11 FR-CORE-1..4; NFR-PERF-1..5
Room framework & rooms §2 Room framework, §4 Initial rooms M12, M13, M14 FR-ROOM-1, FR-MUSIC-1/2, FR-HOME-1
Identity system §5 Identity system M10 FR-ID-1; NFR-SEC-4
Protocol spec & developer experience §6 Protocol specification, §7 Documentation M17, M16 NFR-MAINT-1, NFR-COMPAT-2

Phases

v1 is sequenced into five phases. Each phase ends at a phase gate — a defined point where the backlog status snapshot is updated and Must/Won’t buckets are re-evaluated (see Revisit cadence).

Phase Focus Backlog items Gate — definition of done
0 · Foundation Plugin protocol spec and standardized data models frozen M17, M7 Protocol spec and data models reviewed, committed, and covered by an ADR where the design is non-obvious
1 · Plugin runtime Manifest, discovery, lifecycle, capabilities, debugging, reference plugin M1–M6, M15, M16 Reference local-files plugin returns search results and streams audio end-to-end
2 · Core services Playback engine, queue, unified library, parallel search manager M8, M9, M10, M11 All four services pass their unit/integration acceptance criteria
3 · Rooms & UI Room framework, Music Room, Home (Lobby) M14, M12, M13 Music Room is usable end-to-end: browse, search, play, save to library
4 · Hardening & release Should items, durability, accessibility, release checklist S1, S2, S4, S5, S6, S7, S8 v1 feature-complete; release checklist passed; changelog entry published

Deferred from the v1 phase path

  • Could (C1–C7) — polish and follow-ons: lyrics capability (v2), health dashboard, deduplication, screen reader, i18n, conformance validator, plugin API versioning. Reordered at each sprint planning.
  • Won’t (W1–W12) — explicitly excluded from v1, tracked for v2+: additional rooms, hot-reload, permissions sandbox, SDKs, event bus, accounts/sync, mobile/web, advanced playback, offline downloads, registry, extra extension points, pipe streaming mode (ADR-006).

Cadence

  • Phase gates re-evaluate Must and Won’t; each gate updates the canonical status snapshot in backlog.md.
  • Sprint planning reorders Should and Could.
  • Bucket changes require Tech Lead + Product Owner agreement (R6 in the risk register).
  • Operational status (In progress / Done / Blocked) is tracked live in the Fibery planning layer and reconciled into backlog.md at phase gates — see the sync policy.

Was this page helpful?