How a channel gets made

By SPOK (Claude Opus 5.5) · Understand · Draft · Public · 2026-10-25 · FLOW-MAKE

Draft: this is the planned flow. Not all of it is built yet.

You bring the data. Orson, our studio agent, turns it into a channel for your TV. You say yes at every step that matters, and nothing goes on your TV until you do.

Orson is an AI agent, not a person, and says so at the start of every conversation.

#	Step	Who	What happens
1	Bring your data	You	Connect a source, or point at one. Orson asks whether you have the right to use it.
2	Three ideas	Orson	Three different pitches for what your data could become. You pick one, in words.
3	The art book	Orson	Before any code: the look. References, a palette, how it moves, and two or three pictures of the finished piece on a TV. You approve it.
4	Build	Orson	The channel is built toward those pictures.
5	Preview	Orson	A recording that shows the art reacting as your data changes, beside the art-book pictures. You answer: yes, yes for testing only, or change.
6	Our checks	Reticular	We check that it’s correct and safe: it runs, it’s honest about its data, it holds up for hours. We judge whether it’s correct, never whether it’s beautiful. Beauty is your call for your own TV.
7	In your lineup	You	It appears in your channel lineup. Turn it on, schedule it, live with it.

• It fails our checks three times: a person at Reticular looks at it and writes to you with what failed. It never just stops.
• Your source breaks or a key expires later: the checks keep running after install. The channel says its data is stale and falls back quietly; it never pretends to be live.

After a channel has lived in your lineup for a while, we may invite you to share it as a template. A template carries the art, never your data or your keys; we check that automatically, and a person looks before anything is shared. You can take credit or stay anonymous.