Skip to content

Freshness, season-context, and provenance gates for volatile event metadata #147

Closed

Description

@Jumpstile

Origin

Product-owner requirement from IPTVBoss Discord AED dataset review screenshots/discussion on 2026-09-13.

The observed external failure mode came from an IPTVBoss Discord user report: sports/event descriptions can look polished while containing stale or contextually wrong facts, such as preseason statistics being presented during the regular season, stale game/result data from a previous day, or player/team facts that may no longer be current. ChannelForge must not reproduce this failure mode.

This issue records the failure mode as product evidence and guardrail input only. It is not a claim that ChannelForge currently has the same behavior, and it is not a dependency on IPTVBoss internals.

Problem

Event-channel intelligence is not only about extracting a title/time from provider text. It may also generate or display descriptions, matchup notes, team records, player statistics, standings, venue details, live/final state, or other volatile sports/event facts.

Those facts can become wrong quickly. A description that is grammatically correct but stale is worse than no description because it teaches the user the wrong thing and undermines trust.

Required product rule

ChannelForge must treat volatile event metadata as freshness-bound, season-context-bound, and provenance-bound.

If ChannelForge cannot prove that a volatile fact is fresh enough, applicable to the correct season/competition/week/game state, and sourced from allowed evidence, it must omit that fact or mark it as stale/review-needed. It must not publish or present it as current.

Scope

This applies to:

  • event guide descriptions;
  • matchup summaries;
  • team records;
  • player statistics;
  • standings/playoff implications;
  • injury/roster/trade context;
  • start/final/live state;
  • generated programme descriptions;
  • event-pattern preview/review/acceptance plans where such facts appear;
  • future schedule/source adapters and enriched event intelligence.

Required safeguards

ChannelForge must preserve and evaluate, at minimum:

  • source identity;
  • source type;
  • fetched-at timestamp;
  • source-declared data timestamp when available;
  • event date/time and timezone;
  • league/season/week/round/competition context;
  • whether the statistic is preseason, regular season, postseason, tournament, exhibition, or unknown;
  • applicable team/player identity and roster validity window where evidence exists;
  • freshness TTL by fact type;
  • contradiction state when sources disagree;
  • degraded/stale state when a source is unavailable;
  • confidence and provenance for every included fact.

Behavior requirements

  • Never mix preseason statistics into a regular-season context unless explicitly labeled and intentionally selected.
  • Never carry prior-day game/result state forward as current without freshness proof.
  • Never present roster/player/team facts as current when source evidence is stale or contradictory.
  • Prefer a shorter, safer description over a rich but stale description.
  • If volatile context is stale, produce a plain-language status such as: Event found, but current stats are unavailable or stale. ChannelForge preserved the title/time and omitted unsafe details.
  • Preserve last-known-good event identity separately from volatile descriptive facts.
  • Do not make one source authoritative merely because it repeats itself.
  • Do not treat mirrored sources as independent confirmation.
  • Keep all provider URLs, stream URLs, credentials, private paths, tokens, parser errors, hashes, and generation IDs out of user-facing reports where redaction is required.

Relationship to existing work

Related issues:

This issue tightens the requirements for #121 and #35: event intelligence must not only be deterministic and explainable; it must be fresh, context-correct, and safely degraded when freshness cannot be proven.

Acceptance criteria

  • Volatile event facts have explicit freshness/provenance fields and are excluded or marked stale when those fields are missing or expired.
  • League season context prevents preseason, regular-season, postseason, tournament, and exhibition facts from being mixed silently.
  • Game/result status cannot remain current beyond its TTL without fresh evidence.
  • Player/team/roster facts are either current by evidence or omitted/marked stale.
  • Contradictory facts from multiple sources produce a review/degraded state, not a confident description.
  • Generated event descriptions explain omitted volatile details in beginner-friendly language.
  • Tests cover stale NFL preseason stats during regular season, stale prior-day MLB summaries, stale roster/player facts, unavailable source, contradictory sources, and safe omission.
  • Existing Stage B/C/D/E event-pattern workflows remain candidate-only/report-only until separately authorized for acceptance/publication.

Definition of done

ChannelForge cannot display or publish polished-but-stale sports/event descriptions. Volatile facts are included only when freshness, season context, and provenance support them; otherwise ChannelForge safely omits them, marks them stale, or asks for review.

Activity

  1. Jumpstile commented on Nov 17, 2026

    @Jumpstile
    OwnerAuthor

    Done in #265 (merged). A read-only review traced every path that can put text into an event guide: event guide output carries title, time and channel only. No ChannelForge code generates a statistic, record, result, standing or live/final claim; descriptive text only passes through from the user's own guides (the guide author's data). The safeguards the issue lists already exist as records and a resolver (source identity, fetched-at, source data timestamp, freshness TTL and state, contradiction and stale states, season context in Resolve-ChannelForgeGuideVolatileFacts.ps1), but nothing produces volatile facts yet. Added: a short 'Volatile event facts' rule in ENGINEERING_PRINCIPLES.md and one test that event channel programmes contain only a title even when the provider guide has desc, sub-title and category text. Not verified: Build-Lineup.ps1 line by line, the full suite. Closing; if a future slice adds fact generation or enrichment, this rule and test are the gate. Open question for the owner, not blocking: the One Guide Status and live-now/starting-soon keys are time arithmetic against a passed-in instant and are not written to XMLTV; keep it that way until they carry a user-visible evaluation instant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions