Repository navigation
Description
Parent
- Epic: One Guide, Every Screen — unified television and streaming experience #62 Epic: One Guide, Every Screen
- Six-Month Delivery Gate — fully usable One Guide living-room product by March 2027 #190 Six-Month Delivery Gate
- Related: Event Intelligence Engine — automatic live-event discovery, schedule verification, and learned EPG generation #28, Automatic event discovery — classify channels, resolve identities, and match verified schedules #30, Autonomous Operations — scheduled refresh, multi-guide learning, source drift detection, and zero-touch maintenance #35, EPG Acquisition and Merge — multi-lineup identity, validation, provenance, and deterministic XMLTV #40, Channel Guide Preview — now/next, timeline grid, profiles, and printable lineup #43, Universal Search #63, Universal Live Guide — one normalized timeline across linear TV, live streaming, sports, and scheduled events #186, SER8 Living-Room Reference Client — appliance UX, Harmony control, and platform selection #188
Product-owner priority
Guide quality is the most important product-quality dimension.
A beautiful interface over incomplete, stale, misclassified, duplicated, or misleading programme data is a failed product.
ChannelForge must optimize first for:
- correctness
- completeness
- freshness
- classification quality
- event/program identity
- deduplication
- clear provenance/confidence
- fast discovery from the couch
The presentation layer should then turn that high-quality guide into a set-top-box experience that is easier to browse than a conventional cable grid.
Product outcome
The ChannelForge living-room interface should provide category-first discovery surfaces such as:
- Wrestling
- Football
- Baseball
- Basketball
- Hockey
- Soccer
- Motorsports
- Combat Sports
- Other Sports
- Movies
- TV Shows / Series
- News
- Kids / Family
- Music
- Live Events
- Local
- Favorites / My Stuff
The initial category set may evolve based on real usage, but sports and wrestling must be first-class categories rather than buried under a generic Sports bucket.
Home / category-hub concept
The home surface may use large remote-friendly tiles, for example:
- Guide
- Live Now
- Wrestling
- Football
- Baseball
- Soccer
- Movies
- News
- Search
- Apps
Selecting a category opens an optimized discovery surface rather than forcing every category into the same UI.
Examples:
Wrestling
- On Now
- Tonight
- Coming Up
- WWE
- AEW
- TNA
- NJPW
- MLW / other promotions
- Recently available / catch-up entry points where supported
Football
- Live Now
- Starting Soon
- NFL
- College
- Other leagues
- Team-focused filtering/favorites
Movies
- On Now
- Starting Soon
- New / premieres where supported
- By provider
- By genre
- Search
News
- Live Now
- Local
- National
- Business
- International
- Weather / specialty where useful
These are examples, not rigid final layouts.
Presentation research / invention requirement
Do not assume the conventional horizontal channel-grid is the final answer.
Evaluate and prototype couch-first presentations such as:
- large category tiles
- Now / Next cards
- vertical event lists
- timeline rails
- compact EPG grids
- poster/artwork rows where appropriate
- league/promotion/team grouping
- provider-neutral event cards
- “starting in X minutes” sections
- daypart sections
- hybrid layouts
Different categories may legitimately use different presentation patterns.
The chosen interaction must prioritize:
- Harmony D-pad efficiency
- minimal clicks
- strong focus visibility
- readable distance typography
- quick jump to Now
- quick return Home
- obvious “Watch” action
- simple alternate-source access
- no dependency on pointer/mouse interaction
Guide classification model
Guide content must be categorized from the canonical model, not UI-only string matching.
Classification should support, where applicable:
- content type
- sport
- league
- competition
- team
- promotion
- event type
- movie
- series/episode
- news
- kids/family
- music
- live/scheduled status
- provider
- channel/network
- region
- language
- user tags/favorites
Each classification should preserve evidence/provenance and confidence where inferred.
Guide quality gates
At minimum measure/report:
Accuracy
- correct title
- correct start/stop time
- correct channel/provider association
- correct event identity
- correct teams/promotion/league/category
Completeness
- expected channels/events represented
- missing schedule coverage detected
- missing metadata identified explicitly
Freshness
- fetch time
- source age
- stale-window policy
- changed/postponed/cancelled events updated promptly
Deduplication
- one canonical event/program when multiple providers carry it
- alternate offerings retained without duplicate user-facing event cards
Classification quality
- category and subcategory confidence
- no silent cross-category contamination
- ambiguous classification routed to review/unknown rather than guessed
Availability quality
- distinguish “scheduled” from “actually available to this user”
- retain provider/source evidence
- do not claim entitlement where unknown
Quality-first source policy
Provider-supplied EPG is evidence, not automatic truth.
ChannelForge should use the evidence model from #40/#175 and event intelligence from #28/#30 to:
- compare overlapping sources
- prefer stronger/fresher evidence
- detect disagreement
- repair only when sufficiently supported
- preserve original values and correction provenance
- fail visibly rather than fabricate
User-visible trust cues
The normal user should not see technical confidence scores everywhere, but the UI should make meaningful uncertainty understandable:
- Confirmed
- Updated
- Source unavailable
- Schedule may be stale
- Needs attention
Advanced details can expose source/provenance/confidence.
Performance requirement
Category entry should feel immediate on the SER8.
Precompute/index the guide as necessary so normal operations such as:
- open Wrestling
- open Football
- show Live Now
- show Tonight
- move between events
- open details
do not trigger slow provider fetches in the foreground.
Refresh and normalization belong in the background through #35.
Acceptance criteria
- Category taxonomy is represented in the canonical model, not hard-coded solely in UI.
- At least Wrestling, Football, Baseball, Soccer, Movies, and News have dedicated couch-first views.
- Wrestling has promotion-aware grouping and high-quality schedule/event identity.
- Sports categories are league/team-aware where data permits.
- Each category supports On Now and Coming Up.
- At least two presentation patterns are prototyped/tested before locking the final 10-foot UX.
- Conventional EPG grid remains available where it is useful, but is not the only discovery model.
- Cross-provider duplicate events appear once with multiple offerings.
- Guide-quality metrics and failure states are testable.
- Stale/incomplete/ambiguous guide data is surfaced honestly.
- Harmony Elite navigation is complete without routine keyboard/mouse use.
- Category views integrate with Universal Live Guide — one normalized timeline across linear TV, live streaming, sports, and scheduled events #186 canonical guide and SER8 Living-Room Reference Client — appliance UX, Harmony control, and platform selection #188 SER8 client rather than creating separate guide stores.
- Exact-head docs/screenshots reflect the shipped interaction.
Release impact
This issue is release-driving under #190.
Provider breadth must not outrank guide quality. If schedule pressure forces a tradeoff, prioritize a smaller number of well-supported providers with excellent guide accuracy/classification over a larger provider list with weak or misleading guide data.
Activity
Jumpstile commentedon Sep 27, 2026
Product-owner interaction requirement: category hubs must be directly actionable, not just informational.
Example — Wrestling:
The same interaction contract should apply to Football, Baseball, Soccer, Movies, News, and other category hubs.
Category views therefore need actionable canonical item IDs plus resolved availability/launch metadata from #70/#67, not presentation-only programme cards.
Jumpstile commentedon Sep 27, 2026
Guide-quality refinement: category hubs must be both trustworthy and instant-feeling. #193 adds concrete latency budgets for opening Wrestling/Football/Movies/News, Live Now, details, search, and source resolution on the SER8. Guide refresh/enrichment must not block ordinary browsing.
Jumpstile commentedon Sep 27, 2026
Category/guide UX must satisfy #194: category hubs should be understandable at a glance without instruction, visually polished, readable at TV distance, and tested with untrained users. Guide density must not regress into a desktop-style EPG merely because more metadata is available.
Jumpstile commentedon Sep 30, 2026
Owner scope update — 2026-09-30
The expanded One Guide built-in taxonomy is approved and should move forward:
live-now,starting-soon,football,baseball,basketball,hockey,soccer,wrestling,motorsports,boxing,mma,tennis,golf,rugby,cricket,lacrosse,other-sports,movies,news,kids,entertainment,documentary,comedy.Generic Sports should map to
other-sportsonly when no more-specific recognized sport category is present; unknown XMLTV categories remain omitted.PR #199 has merged into main at
f20c7f034bb473ef196cddeb9ffaa2399675c227. That merge contains the base One Guide API and unavailable-vs-valid-empty fix, but not this expanded taxonomy. The preserved expansion work should continue as a focused follow-up under #191 while #200 proceeds in parallel in its own worktree.Jumpstile commentedon Sep 30, 2026
Coordination note — active parallel lanes
C:\REPOS\ChannelForge.worktrees\issue191-expanded-taxonomy, branchfeature/issue-191-expanded-one-guide-taxonomy.feature/issue-200-one-guide-slice2, currently in the stale-named local worktree pathC:\REPOS\ChannelForge.worktrees\issue198-one-guide-slice1until path cleanup is safe.All lanes share
C:\Temp\CHANNELFORGE-AUTHORITATIVE-STATE.txtas the current owner coordination state.Merge origin/main (PR #202 Live Now) into #191 expanded taxonomy
fix(one-guide): treat Other Sports alias as generic sports for preced…
Jumpstile commentedon Oct 2, 2026
Official wrestling source research — bounded adapter plan (2026-10-02)
This fills the source-specific gap under #191 and complements the existing canonical evidence/provider/matching work in #29, #30, and #175. It is research and a proposed sequence only: no new epic, scope rewrite, implementation, or release certification. Wrestling remains required across WWE, AEW, TNA, NJPW, ROH, and MLW; phasing AEW first and WWE next does not make the other promotions optional.
Promotion-owned sources reviewed
Access and evidence limits
These are verified promotion-owned public pages and field examples, not verified automated-source contracts. I found no public API documentation in the official pages reviewed; API/feed availability remains undocumented, not disproven. I did not establish permission for automated fetching, caching/retention, or redistribution, nor complete market-specific rights for each event. Before production automation, confirm a permitted API/feed or written/terms-supported page-ingestion path, cadence/rate limits, retention/display rights, and territory rights. Do not promise an API or scrape provider pages absent that review.
Bounded acceptance for AEW, then WWE
The AEW slice is complete only when these missing/bad-guide, revision, timezone, cancellation, dedupe and unresolved-availability cases are covered. WWE follows; TNA, NJPW, ROH and MLW remain required promotion coverage.
Jumpstile commentedon Oct 3, 2026
Wrestling event/card v2 proposal — decision packet
Draft proposal artifacts are in PR #204. The design remains synthetic-only and unapproved: v2 links card revisions to one unchanged v1 event assertion in the existing canonical event truth layer. V1 schema/converter stay closed; no production adapter, consumer, or UI behavior is authorized.
Independent technical recommendations (advisory, not architecture approval)
The current decision owner is the Product Owner / Engineering Manager; existing #191 owner dispositions identify @Jumpstile in that role. This issue currently has no assignee, and the repository record names no independent architecture reviewer. Assign that reviewer through the architecture-proposal workflow. These recommendations do not constitute architecture acceptance or product-owner approval.
Source gate and next slice
The #29 source-access gate remains open. #191 research establishes candidate public first-party evidence pages and an MCP access avenue, not automated-use, caching, retention, display, or territory rights. No live source was queried. After formal architecture acceptance and source rights, the next bounded slice is one permitted AEW schedule-window adapter under #29: ordinary v1 event assertion plus one linked v2 card observation per revision, report-only Guide Intelligence, offline synthetic tests. No #30 consumer or #191 UI work in that slice.
Related to #29, #30, and #36. No closure or approval is claimed.
Jumpstile commentedon Oct 3, 2026
Source-evidence cross-reference for the #191 wrestling discovery gate: the parent-provided 2026-10-03 community-source research, exact source/document URLs, sample findings, licensing limits, and bounded adapter direction are recorded once in #29 comment 5964911791. For #191, Wikipedia text is only separately attributed community evidence, not promotion-approved truth or complete card coverage; it does not close first-party source rights, event coverage, or card-v2 approval. No live source was queried in this owner session.
Jumpstile commentedon Oct 3, 2026
Owner direction — personal, continuously researched guide (2026-10-03)
This records the owner's explicit Oct 3 direction, including “Treat every individual sports, ppv, etc channel as a little research project” and confirmation of the interpretation below. This is required product scope, not merely an ecosystem suggestion.
Required behavior
Acceptance examples
The owner approved the offline, text-only Wikipedia supplemental development direction with revision/time/attribution/uncertainty, and explicitly instructed implementation of cross-channel fuzzy matching/learned aliases. This is not approval to merge PR #204, activate live production ingestion, purchase sources, create credentials or bypass source restrictions.
Routing and sequencing
Reuse existing modules/contracts and prior implementations before adding code: #29 source/event evidence; #30 programme/event matching; #31 learned aliases/history; #35 refresh/LKG operations; #36 storage; #190 delivery plan. Keep PR #204's architecture review boundary explicit. Do not create a monolithic scraper or one agent per channel. Phase implementation against the existing deadlines without treating remaining category coverage as optional.
Existing #191 labels (type:feature, priority:high, component:ux) remain appropriate; no arbitrary milestone was assigned to this cross-cutting requirement. Component slices retain their established milestones and dependencies.
feat(guides): add report-only XMLTV comparison (#191)
6 remaining items
Jumpstile commentedon Nov 13, 2026
Logo plan for this issue is now merged to main in three PRs:
CI on #219 passed in full (quality-gates, secret-scan, CodeQL, Gitleaks, Semgrep, SBOM, Windows security tests). Before merge, the lane checks of the PR 3 and fingerprint files ran 0 failures (7 test files for PR 3, 20 test files for the fingerprint work).
Not verified: a full Build-Lineup run end to end with the new setting, and the whole local suite outside CI. Leaving this issue open until a real lineup build shows the logos.
🤖 Generated with Claude Code
https://claude.ai/code/session_01NzHAckAcs78Lu3rv8Gqgrf
feat: report how channels are grouped, with overrides (#191 slice 1) (#…
feat: show a category check in the build summary (#191 slice 2) (#240)
feat: check programme titles against the channel category (#191 slice…
Add a report-only guide quality scorecard (#191) (#270)
Check the provider group against league tags when classifying a chann…
Stop the guide scorecard from reporting Pass on gates it cannot measu…
Jumpstile commentedon Nov 17, 2026
Progress on Phase 1 (guide truth), 2026-11-17:
No release or tag.
Jumpstile commentedon Nov 17, 2026
Real-lineup scorecard result after the two fixes (read-only run on copies of the real 404-channel lineup; 36,068 programmes from one guide; no URLs or provider details copied). Overall: Review.
Gap found: no existing code turns a real playlist plus guide into the evidence records that the guide readiness check needs (the evidence builder is only called by tests), so Availability stays blind and Accuracy cannot see contradictions. Next slice: a small step that builds that evidence from existing data, then re-run. Not verified: whether the 142 unknown and 62 no-programme channels are expected.
Build guide evidence from a playlist and one guide so readiness can r…
Jumpstile commentedon Nov 17, 2026
Evidence builder merged (PR 274): guide readiness now runs on a real playlist plus one guide. Real 404-channel lineup copy: 332 channels safe candidates, 72 unresolved (62 have no programmes, 10 have programmes but a tvg-id the existing builder rejects). Availability goes from NotMeasured to Review. Accuracy stays NotMeasured with one guide. Next: give those 10 a stable hashed reference in the mapper (no change to the frozen builder), then re-run.
Keep channels with programmes out of the missing group when the tvg-i…
Jumpstile commentedon Nov 17, 2026
Merged: ID fix for the evidence step (PR 275). On the real 404-channel lineup copy, the 10 channels whose tvg-id has spaces or symbols but that do have programmes are no longer counted as missing (read-only run; raw ids not written anywhere). Still unresolved are the channels that truly have no programmes (62 in the earlier run). Availability stays Review for that reason. Next: developer docs for the scorecard and the evidence step. Open for #191: a look at the 62 channels with no guide data, and the 142 unknown categories (mostly PPV, music and adult groups).
Document the guide quality scorecard and the playlist evidence step (#…
Jumpstile commentedon Nov 17, 2026
Docs merged: developer guide section for the scorecard and the evidence step.
Read-only look at why 62 of 404 playlist channels have no guide data (copies of the real lineup; no URLs or provider details copied):
Not verified: whether the 3 pay-per-view gaps and the one sports gap come from the guide source or from ChannelForge.
Owner decisions pending: (1) count adult and music groups as no-guide-expected so the 62 shrinks to about 4; (2) whether to add Music, Pay-per-view and Adult category keys (new vocabulary).