Broadcast channels
A television-like shell over fixture video files: channel schedules, flipping, and a golden TV frame, with no live video site in CI.
This is a small site spec on Spekkr, published by lume. It is listed with the other specs. Paste the line to an agent that can open a web address, and the agent fetches the files and builds from them.
- Spec
lume/broadcast-channels- Version
- 0.2.2
- Published by
- lume
- Updated
- 15 Nov 2026
Build this spec
Build the spec at https://spekkr.com/lume/broadcast-channels/start.md.
Paste this to your AI agent. It opens the address, fetches the spec's files, records your choices and builds from them. Nothing to install, no account.
Published by lume.
What does the result look like?
What can I customize?
Your choices go into the line you copy. Anything else is yours to edit, but it leaves the tested path.
What do I get?
-
spec.mdRequirements and acceptance checks.Broadcast channels
What this builds
A television you can flip through, with a guide and a channel number, playing local fixture videos on a schedule. It has the feel of evening channels, but it is not a front-end for a live commercial video site, and it does not use that site's name in the product id. Checks use fixture files and an injected clock. A hook fails if a known video-host is contacted.
Read
spekkr.inputs.jsonfirst.titleis on the guide.clockis the injected now.setchooses the schedule.guideandchromechange the picture.Out of scope
- A live commercial video site, or that site's name in the product id.
- Network or a real programme guide in the checks.
- A tuner or a broadcast licence.
Requirements
Each requirement has an id. Checks name the id they cover.
R1. Schedules and flipping
- At the fixture time, each channel's current item is the one in
fixtures/evening-2026-01-15-20-15.json. - A flip up or down moves to the next channel in the list and plays that channel's current fixture file from a documented offset (the time into the programme).
- A channel with no item at that time shows an off-air slide.
Accept when: the current items match, a flip from channel 3 to 4 plays the listed file at the listed offset, and an empty slot shows off-air.
R2. No live host
- Videos are local files listed in the set. A fetch hook fails if a known video-host or CDN is contacted.
- Goldens: the guide, channel 3 playing, a mid-flip frame, and the off-air slide.
- One command runs the schedule, the flip, the hook, and writes the frames. The clock is injected. No network.
Accept when: the hook stays quiet, and the four frames match the goldens.
R3. Inputs
- The build reads
spekkr.inputs.json. Settings label the UI, options turn features on or off, and a swap must be one of its choices. - A value outside a stated range, or a swap that is not one of its choices, is refused before the app starts its checks, with a message that names the key.
Accept when: the default inputs render, an illegal swap is refused by name, and changing a visible setting (for example the title) shows up in a later check.
R4. Checks and report
- One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them.
- Checks do not need a network, a paid API, or physical hardware.
Accept when: the command passes at the defaults, and a deliberately broken fixture or a wrong price fails it.
Verification
Channel schedules and flipping are tested with fixture video files and an injected clock. A fetch hook fails if a live video host is contacted. A golden TV-frame screenshot is checked. The product does not use a commercial video site's name in its id.
Definition of done
- Every acceptance check above runs from one command, and all pass at the person's inputs.
- A README says how to flip channels, how to add a fixture, and how to run the checks.
# Broadcast channels ## What this builds A television you can flip through, with a guide and a channel number, playing local fixture videos on a schedule. It has the feel of evening channels, but it is not a front-end for a live commercial video site, and it does not use that site's name in the product id. Checks use fixture files and an injected clock. A hook fails if a known video-host is contacted. Read `spekkr.inputs.json` first. `title` is on the guide. `clock` is the injected now. `set` chooses the schedule. `guide` and `chrome` change the picture. ## Out of scope - A live commercial video site, or that site's name in the product id. - Network or a real programme guide in the checks. - A tuner or a broadcast licence. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Schedules and flipping - At the fixture time, each channel's current item is the one in `fixtures/evening-2026-01-15-20-15.json`. - A flip up or down moves to the next channel in the list and plays that channel's current fixture file from a documented offset (the time into the programme). - A channel with no item at that time shows an off-air slide. Accept when: the current items match, a flip from channel 3 to 4 plays the listed file at the listed offset, and an empty slot shows off-air. ### R2. No live host - Videos are local files listed in the set. A fetch hook fails if a known video-host or CDN is contacted. - Goldens: the guide, channel 3 playing, a mid-flip frame, and the off-air slide. - One command runs the schedule, the flip, the hook, and writes the frames. The clock is injected. No network. Accept when: the hook stays quiet, and the four frames match the goldens. ### R3. Inputs - The build reads `spekkr.inputs.json`. Settings label the UI, options turn features on or off, and a swap must be one of its choices. - A value outside a stated range, or a swap that is not one of its choices, is refused before the app starts its checks, with a message that names the key. Accept when: the default inputs render, an illegal swap is refused by name, and changing a visible setting (for example the title) shows up in a later check. ### R4. Checks and report - One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them. - Checks do not need a network, a paid API, or physical hardware. Accept when: the command passes at the defaults, and a deliberately broken fixture or a wrong price fails it. ## Verification Channel schedules and flipping are tested with fixture video files and an injected clock. A fetch hook fails if a live video host is contacted. A golden TV-frame screenshot is checked. The product does not use a commercial video site's name in its id. ## Definition of done - Every acceptance check above runs from one command, and all pass at the person's inputs. - A README says how to flip channels, how to add a fixture, and how to run the checks.
-
design.mdFixture schedules, flip offsets, and the no-live-host rule.Design
This file fixes the parts that are easy to get wrong. The language and tools are up to you, as long as the numbers here hold.
Evening set
Channels 1–6, times and fixture file paths in
sets/evening.json. Offsets are computed from the injected clock minus the programme start, and must match the file to 0.2 s.Screenshot tolerance
8 levels, 98% of pixels (video frames may use a 12-level, 96% tolerance if the decoder is not bit-exact, as noted in the fixture).
Inputs
Key Label Default Notes titleSet title Evening programmes Shown on the guide. clockFixture time 2026-01-15T20:15:00 The injected now, local to the fixture schedule. guideShow a programme guide on A list of channels and times. chromeShow TV chrome on A bezel and a channel number. setChannel set evening A shipped schedule plus local fixture videos. No live video host. Acceptance at the defaults
The numbers, names and fixture paths already in this file are the authority. Where a later table or a shipped fixture file disagrees with prose, the table or the fixture wins.
Fixture Role fixtures/evening-2026-01-15-20-15.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.sets/evening.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.spekkr.inputs.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.Golden frames are compared at 1400 by 1000 CSS pixels unless a requirement names another size. Tolerance, unless a tighter figure is given above: 8 levels, 98% of pixels, with motion, cursors and clocks frozen as this file says. A build's goldens are of that build; they do not have to match a shipped reference preview pixel-for-pixel if the tool or the type is different, but they do have to match this file's layout, counts and copy.
Screenshots
These pictures are headless-Chrome captures of the working reference in
reference/preview.html, at the default inputs. They are not drawings of a product that has not been built. The first picture is the one Spekkr shows on the spec's card. A build may ship its own goldens; those goldens are of that build and do not have to match these frames pixel-for-pixel.File What it shows shots/evening.pngChannel 4 at 20:15 on 15 January 2026, The Harbour Hour. How to verify
- Run the checks at the default inputs, without a network.
- Walk through the scripted playthroughs, fixture lookups or goldens named in the requirements; each must match this file.
- Repeat once at the person's inputs when they differ from the defaults.
- Channel schedules and flipping are tested with fixture video files and an injected clock. A fetch hook fails if a live video host is contacted. A golden TV-frame screenshot is checked. The product does not use a commercial video site's name in its id.
# Design This file fixes the parts that are easy to get wrong. The language and tools are up to you, as long as the numbers here hold. ## Evening set Channels 1–6, times and fixture file paths in `sets/evening.json`. Offsets are computed from the injected clock minus the programme start, and must match the file to 0.2 s. ## Screenshot tolerance 8 levels, 98% of pixels (video frames may use a 12-level, 96% tolerance if the decoder is not bit-exact, as noted in the fixture). ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Set title | Evening programmes | Shown on the guide. | | `clock` | Fixture time | 2026-01-15T20:15:00 | The injected now, local to the fixture schedule. | | `guide` | Show a programme guide | on | A list of channels and times. | | `chrome` | Show TV chrome | on | A bezel and a channel number. | | `set` | Channel set | evening | A shipped schedule plus local fixture videos. No live video host. | ## Acceptance at the defaults The numbers, names and fixture paths already in this file are the authority. Where a later table or a shipped fixture file disagrees with prose, the table or the fixture wins. | Fixture | Role | | --- | --- | | `fixtures/evening-2026-01-15-20-15.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `sets/evening.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `spekkr.inputs.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | Golden frames are compared at 1400 by 1000 CSS pixels unless a requirement names another size. Tolerance, unless a tighter figure is given above: 8 levels, 98% of pixels, with motion, cursors and clocks frozen as this file says. A build's goldens are of that build; they do not have to match a shipped reference preview pixel-for-pixel if the tool or the type is different, but they do have to match this file's layout, counts and copy. ## Screenshots These pictures are headless-Chrome captures of the working reference in `reference/preview.html`, at the default inputs. They are not drawings of a product that has not been built. The first picture is the one Spekkr shows on the spec's card. A build may ship its own goldens; those goldens are of that build and do not have to match these frames pixel-for-pixel. | File | What it shows | | --- | --- | | `shots/evening.png` | Channel 4 at 20:15 on 15 January 2026, The Harbour Hour. | ## How to verify 1. Run the checks at the default inputs, without a network. 2. Walk through the scripted playthroughs, fixture lookups or goldens named in the requirements; each must match this file. 3. Repeat once at the person's inputs when they differ from the defaults. 4. Channel schedules and flipping are tested with fixture video files and an injected clock. A fetch hook fails if a live video host is contacted. A golden TV-frame screenshot is checked. The product does not use a commercial video site's name in its id.
-
tasks.mdBuild tasks in order, each with a check.Tasks
Work in order. Finish a task's check before starting the next.
- Set up. Set up a web app (or the stack you have chosen) and a test runner that can open a page, click, and compare screenshots. Read
spekkr.inputs.jsonfirst. Check: a blank or heading page loads, and an empty test run passes. - Schedules and flipping (R1). Build what
R1. Schedules and flippingasks for, to the numbers indesign.md. In particular: At the fixture time, each channel's current item is the one infixtures/evening-2026-01-15-20-15.json. Check: theR1. Schedules and flippingacceptance checks pass. - No live host (R2). Build what
R2. No live hostasks for, to the numbers indesign.md. In particular: Videos are local files listed in the set. A fetch hook fails if a known video-host or CDN is contacted. Check: theR2. No live hostacceptance checks pass. - Inputs (R3). Build what
R3. Inputsasks for, to the numbers indesign.md. In particular: The build readsspekkr.inputs.json. Settings label the UI, options turn features on or off, and a swap must be one of its choices. Check: theR3. Inputsacceptance checks pass. - Checks and report (R4). Build what
R4. Checks and reportasks for, to the numbers indesign.md. In particular: One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them. Check: theR4. Checks and reportacceptance checks pass. - Goldens. Capture the frames named in
design.mdat the defaults, with motion frozen where the file says so. Compare them within the stated tolerance. Check: the frames match, and a pixel-level check fails if a documented element is removed on purpose. - Finish. Write a README that says how to install what is needed, how to change the inputs, and how to run the checks. Run the one command from a clean folder. Check: every item under Definition of done in
spec.mdis true.
# Tasks Work in order. Finish a task's check before starting the next. 1. **Set up.** Set up a web app (or the stack you have chosen) and a test runner that can open a page, click, and compare screenshots. Read `spekkr.inputs.json` first. Check: a blank or heading page loads, and an empty test run passes. 2. **Schedules and flipping (R1).** Build what `R1. Schedules and flipping` asks for, to the numbers in `design.md`. In particular: At the fixture time, each channel's current item is the one in `fixtures/evening-2026-01-15-20-15.json`. Check: the `R1. Schedules and flipping` acceptance checks pass. 3. **No live host (R2).** Build what `R2. No live host` asks for, to the numbers in `design.md`. In particular: Videos are local files listed in the set. A fetch hook fails if a known video-host or CDN is contacted. Check: the `R2. No live host` acceptance checks pass. 4. **Inputs (R3).** Build what `R3. Inputs` asks for, to the numbers in `design.md`. In particular: The build reads `spekkr.inputs.json`. Settings label the UI, options turn features on or off, and a swap must be one of its choices. Check: the `R3. Inputs` acceptance checks pass. 5. **Checks and report (R4).** Build what `R4. Checks and report` asks for, to the numbers in `design.md`. In particular: One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them. Check: the `R4. Checks and report` acceptance checks pass. 6. **Goldens.** Capture the frames named in `design.md` at the defaults, with motion frozen where the file says so. Compare them within the stated tolerance. Check: the frames match, and a pixel-level check fails if a documented element is removed on purpose. 7. **Finish.** Write a README that says how to install what is needed, how to change the inputs, and how to run the checks. Run the one command from a clean folder. Check: every item under Definition of done in `spec.md` is true.
- Set up. Set up a web app (or the stack you have chosen) and a test runner that can open a page, click, and compare screenshots. Read
-
reference/preview.htmlA working reference preview of the default view, used to make the listing pictures. A build does not have to start from this file. -
reference/fonts/fonts.cssWebfont faces for the reference preview. -
reference/fonts/Geist.ttfGeist variable typeface for the reference preview. -
reference/fonts/GeistMono.ttfGeist Mono variable typeface for the reference preview. -
reference/fonts/Fraunces.ttfFraunces variable typeface for the reference preview. -
reference/fonts/Fraunces-Italic.ttfFraunces italic variable typeface for the reference preview.
Is it for me?
- Kind
- small site
- Platforms
- web
- Tools
- TypeScript
What does it need?
- Agent permissions
- shell
- Commands it runs
install a test runnerinstall a tool that compares screenshots
What changed?
- 0.2.215 Nov 2026Names what it builds.
- 0.2.114 Nov 2026Add animated loop to the listing shots.
- 0.2.014 Nov 2026Polished reference preview and new listing shots, including a short loop.
- 0.1.014 Nov 2026First version.
For agents: start.md says how to build this spec, spec.json holds everything on this page, and bundle.tar.gz holds its files.