Skip to content

Channels

Channels and what they play. A channel’s lineup becomes an ordered schedule, and the reconcile engine keeps each channel’s programming current for whichever backend plays it. Operator edits and approved proposals each have one write path. Self-updating channels are re-curated here, Home’s channel ideas come from here, and so does who is watching now.

One area of the package map.

Imports from other areas

  • platform · 39 imports — the store every channel write goes through, the jobs and settings behind reconcile and re-curation, the activity feed, the language model for recommendations, and the holiday, language and audience-rating vocabularies
  • library · 10 imports — the titles a channel plays: library/provision keys and states, library/inventory breakanalysis, and library/titlesearch candidates for re-curation
  • proposals · 9 imports — binding an approved proposal into a channel, and re-curating a self-updating channel through the suggester
  • filler · 3 imports — asking the filler engine for the pod that fills a break
  • playout · 2 imports — handing reconciled programming to the backend that plays it: Loomarr’s own playout engine or playout/tunarr

Packages

  • channels · 5 importers · → channels/schedule, filler/clips, filler/language, filler/pod, library/inventory, library/provision, platform/jobs, platform/rating, platform/settings, platform/store, platform/store/activitystore, platform/store/channeldatastore, platform/store/channelstore, platform/store/librarystore, platform/store/proposalstore, playout, playout/tunarr Channel reconcile engine (design §9/§18): the conductor that turns a store.Channel’s approved lineup + live availability into durable desired state for whichever playout backend owns it.
  • channels/approval · 2 importers · → channels/schedule, library/provision, platform/rating, platform/store, platform/store/activitystore, platform/store/channelstore, platform/store/proposalstore, proposals, proposals/accept Plans how an APPROVED proposal changes a channel (§7): create it on first approval, patch it (preserving operator-owned fields) on re-approval or refine.
  • channels/edit · 3 importers · → channels/approval, channels/schedule, library/provision, platform/activity, platform/store, platform/store/activitystore, platform/store/channelstore One write path for an operator’s channel changes (§7): creating a hand-made channel, and every edit after it — the PATCH form, an icon or watermark upload, a detach.
  • channels/growth · 1 importer · → channels/edit, channels/schedule, library/provision, platform/holidayvocab, platform/jobs, platform/llm, platform/rating, platform/settings, platform/store/channelstore, platform/store/librarystore, platform/store/proposalstore, proposals, proposals/accept, proposals/suggest, proposals/workflow Decides what may join a channel by itself (#4140 step 2, #4333): the line its seeds draw, how a library title sits against that line, how big the channel should be, and the nightly fill that adds the titles that fit.
  • channels/ideas · 2 importers · → library/provision, platform/holidayvocab Builds library-grounded channel ideas for Home (#1665): what the household’s own library could make into a channel that nothing plays yet, and what a holiday ahead could fill.
  • channels/recommend · → platform/llm Defines inert Channel Concepts and the hermetic evaluator used to certify channel-recommendation models.
  • channels/recurate · 1 importer · → channels/schedule, library/provision, library/titlesearch, platform/jobs, platform/settings, platform/store, platform/store/channeldatastore, platform/store/channelstore, platform/store/proposalstore, proposals, proposals/accept, proposals/suggest Scheduled channel re-curation (programming-design §8.2): a self-updating channel that periodically re-evaluates its intent against the current library and evolves its lineup — preferring in-library matches, weighting net-new acquisitions by quality + intent, and NEVER bypassing the approval gate.
  • channels/schedule · 35 importers · → library/inventory, library/provision, platform/holidayvocab, platform/langcode, platform/rating Scheduler domain (design §9): the Channel identity, the DesiredLineup / Slot model, and the pure computation that turns an approved lineup plus live availability into ordered desired programming.
  • channels/viewing · 5 importers · → platform/store, platform/store/channelstore Tracks who is watching which channel right now, from the players’ own playlist polls (#1662).