A Quilt sheet IS a radio theater. Characters are cells. The setting is a cell. The director is a cell. TTS output is a cell. User input is a cell. The same sheet can be opened as a UI, a system API, or a servo controller.
The idea: a Quilt sheet describes an improv performance. Each cell is a typed piece of state. The director cell decides whose turn it is. The listening cell is open for user input. The TTS output cells speak each character's line. You can pause, interject, or let the show play out.
Below: the live Quilt sheet (left) and the stage (right). The sheet updates as the performance unfolds. The cells are the actors. The stage is what they see.
A Quilt sheet is not a UI. It's a typed, reactive graph of state. You can open the same sheet as a web form (the form above), as a REST API (any cell is addressable at quilt://stage/scene), as a servo controller (each cell becomes a GPIO pin with an encoder), or as an LLM prompt (the cell graph is the structured context). The "interface" is just one rendering of the cells. There are infinitely many. The cells are the universal interface primitive.
This is the far-future inverse of how we write software today. Today: write a UI, then a backend, then a model. Tomorrow: write a cell graph, then open it as any of those.