From 810eb59b6ff754dd42f39e92a2d67ead4091aa50 Mon Sep 17 00:00:00 2001 From: Jumpstile Date: Mon, 16 Nov 2026 23:14:53 -0500 Subject: [PATCH] Reorder the roadmap to match the new milestone order The roadmap now lists the same nine milestones as GitHub: Foundation, Guides and Events, First Usable Alpha, Review UX and GUI, Identity and Registry, Source Operations and Stream Health, Policy and Extensibility, Autonomous Operations, and Future Scope. A short note maps the old roadmap numbers cited in older documents to the new ones. Co-Authored-By: Claude Sonnet 5.5 Claude-Session: https://claude.ai/code/session_01NzHAcjThVoUGWWfXrYWsNh --- ROADMAP.md | 104 +++++++++++++++++++++++++++++++++++------------------ 1 file changed, 70 insertions(+), 34 deletions(-) diff --git a/ROADMAP.md b/ROADMAP.md index 7d413a71..6c9bca33 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -1,6 +1,16 @@ # Roadmap -## Milestone 0 - Engineering Foundation +The milestones below match the GitHub milestones. Work goes in this order: get the guides and events right, ship a first usable alpha, then build the rest on top of it. Issue numbers are listed on GitHub, which is the source of truth. + +Older documents (some ADRs and code comments) cite "Roadmap Milestone 0" to "Roadmap Milestone 5" from before 2026-11-16. That old numbering maps to the milestones below like this: + +- Old Milestone 0 (Engineering Foundation) is Milestone 0. +- Old Milestone 1 (Alias Engine) and old Milestone 2 (Confidence Engine) are Milestone 4. +- Old Milestone 3 (GUI Foundation) is Milestone 3. +- Old Milestone 4 (Provider/EPG Engine) is Milestone 1. +- Old Milestone 5 (Production Build) is Milestones 2 and 5. + +## Milestone 0 - Engineering Foundation and Direction Goal: make the project safe, understandable, and durable before expanding features. @@ -13,38 +23,36 @@ Expected outcomes: - Lessons learned discipline. - GitHub Issues as project memory. - Automated secret scanning. +- Path-safety checks at every place that writes a file. -## Milestone 1 - Alias Engine +## Milestone 1 - Guides and Events -Goal: make alias resolution deterministic, explainable, and reviewable. +Goal: build a correct guide for every channel, including live-event channels, with no manual steps. Expected outcomes: -- Canonical alias model. -- Alias conflict detection. -- Alias review reports. -- Regression tests for known aliases. -- Safe fallback when no alias is known. +- Provider and guide source validation. +- Guide (EPG) acquisition and deterministic merge, with provenance. +- Logos and categories checked before a user accepts anything. +- Guided setup with multiple sources. +- Automatic event guides: finding event channels, agreeing on event times, and a guide entry for each. +- Optional per-channel override when the automatic guess is wrong. -## Milestone 2 - Confidence Engine +## Milestone 2 - First Usable Alpha -Goal: score channel identity evidence and explain confidence. +Goal: a person can install ChannelForge and get a working lineup and guide. Expected outcomes: -- Evidence model. -- Confidence scoring. -- Drift detection. -- Explainable decision reports. -- Review queue for ambiguous matches. - -### Current slice status - -Stage A and Stage B now provide the read-only evidence and native event-pattern candidate contracts. Stage B accepts representative examples or Stage A evidence, extracts structured channel/event fields, normalizes and cross-checks timezone representations, reports deterministic confidence/provenance/review state, and detects naming drift without adopting or publishing a rule. Schedule adapters, persistent learned knowledge, expert overrides, automatic relearning, and guide publication remain future work. +- Target-specific outputs that are deterministic. +- Parity with the everyday features of the tool it replaces. +- Integration checks for paths, permissions, and reachability. +- Windows portable bundle with upgrade and a clean-machine test. +- The First Usable Alpha release checklist. -## Milestone 3 - GUI Foundation +## Milestone 3 - Review UX and GUI -Goal: establish the first GUI-first workflow for preview, review, approval, and recovery. +Goal: a first GUI-first workflow for preview, review, approval, and recovery. Expected outcomes: @@ -54,26 +62,54 @@ Expected outcomes: - Explainable decisions surfaced to users. - Recovery path for mistakes. -## Milestone 4 - Provider/EPG Engine +## Milestone 4 - Identity and Registry -Goal: make provider and EPG ingestion reliable, validated, and source-of-truth driven. +Goal: make channel identity deterministic, explainable, and reviewable, then score the evidence. Expected outcomes: -- Provider source validation. -- EPG source validation. -- Local-only provider config workflow. -- Deterministic fixture inputs. -- CI validation for source data. +- Canonical alias model, conflict detection, and review reports. +- Safe fallback when no alias is known. +- Evidence model, confidence scoring, and drift detection. +- Review queue for ambiguous matches. +- Station registry and fast local storage. -## Milestone 5 - Production Build +### Current slice status + +Stage A and Stage B now provide the read-only evidence and native event-pattern candidate contracts. Stage B accepts representative examples or Stage A evidence, extracts structured channel/event fields, normalizes and cross-checks timezone representations, reports deterministic confidence/provenance/review state, and detects naming drift without adopting or publishing a rule. Schedule adapters, persistent learned knowledge, expert overrides, automatic relearning, and guide publication remain future work. -Goal: produce guarded production outputs with backups, approval gates, and release discipline. +## Milestone 5 - Source Operations and Stream Health + +Goal: keep sources healthy and recover safely when something breaks. Expected outcomes: -- Deterministic build outputs. -- Path-safety checks. -- Explicit production approval. +- Source refresh status, change previews, and last-known-good recovery. +- Bounded stream-health checks and stable fallback order. +- Desired-state reconciliation with verified deploys. +- Backup pools and a Plex channel budget. - Backup and restore workflow. -- Release checklist enforcement. + +## Milestone 6 - Policy and Extensibility + +Goal: shareable policy and a stable way to add adapters. + +Expected outcomes: + +- Versioned policy packs and safe sync. +- AI-assisted rule authoring that is review-only. +- A stable adapter SDK. + +## Milestone 7 - Autonomous Operations + +Goal: scheduled operations that need little attention. + +Expected outcomes: + +- Scheduled refresh and notifications. +- Bounded capacity tests. +- Optional viewing analytics. + +## Milestone 8 - Cross-Service Discovery and Future Scope + +Goal: backlog only. One guide across linear TV and streaming services. It is not part of the active lineup work.