Skip to content

feat: detect event channels and report them (#175, event slice 1) - #252

Merged
Jumpstile merged 1 commit into
mainfrom
feat/event-channel-detector
Nov 14, 2026
Merged

Jumpstile merged 1 commit into
mainfrom
feat/event-channel-detector

Conversation

@Jumpstile

Copy link
Copy Markdown
Owner

Slice 1 of docs/planning/EVENT-AWARE-CHANNELS-DESIGN-NOTE.md (issue #175, contract event-channel/v2). Report only.

  • New Get-ChannelForgeEventChannelCandidate rates each channel high, medium or low as an event channel, with plain reasons. Rules come from a read-only measurement of two real guides (28,239 and 6,100 channels):
    • A PPV / Pay Per View name is high (lowered to medium only with 3 or more different real titles and at most half placeholder time).
    • Another event word (Event, UFC, WWE, AEW, Boxing, Fight, Wrestling, Live Event) with over half placeholder time is high; otherwise medium.
    • Filler alone is NOT a signal (it flagged about 190 normal off-air channels in the measurement). Block length, titles per day and venue text are not used.
    • Placeholder time = a title from one small filler list, a title equal to the channel name, or a generic word such as "pay per view".
  • New Get-ChannelForgeEventChannelSummaryLines and one report block in scripts/Build-Lineup.ps1. A failure is one warning and never changes the build.
  • Nothing hashed, no state file, no byte of any guide, playlist or candidate changes. Frozen contracts untouched.
  • Design note part A updated to match the measured signals.

About 128 product lines plus 5 tests. Verified locally (pwsh): EventChannelCandidate 5, CategorySummary 3, XguideSummary 9, BuildLineupCandidateOnly 3, BuildLineupIdentityBinding 9, BuildLineupFailedGuideSource 3, all 0 failed. Not verified: full suite (CI), Windows PowerShell 5.1, and the detector on the real guides themselves (synthetic fixtures only). The 6-hour limit for the low rating is a guess.

Part of #175.
🤖 Generated with Claude Code

https://claude.ai/code/session_01NzHAckAcs78Lu3rv8Gqgrf

Add a detector that rates channels high, medium or low as event channels (PPV, Pay Per View and similar) from the channel name, category and how the provider guide titles behave, tuned on measured real guides. Report only: one section in the build report, nothing hashed, no guide or playlist byte changes. Update the design note signals to match what was measured.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NzHAckAcs78Lu3rv8Gqgrf
@Jumpstile

Copy link
Copy Markdown
Owner Author

Real-guide check of the detector (read only, EPG Ripper and Jesmann US): 21 channels rated high, no false positives seen. Every channel with PPV or Pay Per View as a whole word was rated high (9 of 9). Two small misses: names like "PPV1" to "PPV4" are not matched, and a title that echoes the channel name with a small difference counts as real. Both are one-line fixes, planned as a small follow-up PR after this one merges. The medium-confidence rule behaved as intended: channels with real schedules stayed at medium.

Not verified on real data: the "low" rule (XMLTV has no category).

@Jumpstile
Jumpstile merged commit 86701b0 into main Nov 14, 2026
11 checks passed
@Jumpstile
Jumpstile deleted the feat/event-channel-detector branch November 14, 2026 16:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant