We imagine a Saga as the higher level of complexity above Scenes and Beats. A saga is like a mini play made up of multiple scenes, often developed over a six-week workshop cycle (a 42 day rhythm). In this format we might create one scene per week, either as a whole group or with smaller Writers Room groups of twos or threes each producing their own. This results in somewhere between four and fifteen scenes. The task of a saga is to weave those scenes into a coherent narrative that can be performed or published. We can imagine it as a podcast with a live audience, recorded and archived at the end of the six weeks, or as a longer publication such as the combined work of all students at the end of a year. We imagine sagas as both performative and filmic. In theatre form, we can enact the work physically using methods similar to playback theatre (such as standing up, moving around, acting out scenes, or bringing in recordings made during the week). This improvisation is punctuated by freeze frames and review moments before culminating in a final summary performance. Such a saga might be six or eighteen minutes long and presented to an audience, followed by panel discussion and questions, with the whole performance recorded and added to the wiki. Alternatively, a saga can take the shape of a filmmaking episode where generative AI produces short visual scenes. These can be stitched into a sequence with text interludes, silent-movie style, to present the workshop’s results. The performative and filmic forms can also be combined. We imagine another dimension as the Saga Map. This maps the different scenes into a nonlinear narrative graph where multiple pathways and climaxes can be explored. A user can follow a critical path through the map, experiencing scenes as live performances, recorded theatre pieces or AI-generated sequences. These might be brief 16-second episodes (such as those made possible by emerging video technologies) or longer arcs when the technical support allows. The map itself can become interactive, functioning as an evolving visual novel or cinematic game. Taken together, these sagas can be published every six weeks or at larger scales such as every 42 elements, forming chapters of a guide. In this way sagas turn cycles of creative work into living, shareable narratives.
https://transcript.myth.garden/assets/saga-technology/Saga%20Technology.wav Saga Technology
# Summary
**Tweet-length summary** A Saga is the next step after Beats and Scenes: a six-week creative arc that blends theatre, film, maps and improvisation into living narratives. Performed, recorded or published, sagas turn cycles of writing into stories worth sharing. --- # Saga: From Scenes to Living Narratives A Saga is the higher level of complexity that emerges from Scenes and Beats. It is best understood as a mini play or performance piece composed of multiple scenes, often developed across a six-week workshop (a 42 day cycle). In this period, groups typically generate between four and fifteen scenes depending on the size of the Writers Room. For example, smaller pods of two or three might each develop their own weekly scene, which can then be combined into a larger narrative. The purpose of a saga is to bring those scenes together into a coherent storyline that can be shared as a public performance, recorded as a podcast, or published as a lasting archive of collaborative work. Over longer timeframes, sagas can scale into collections, such as an entire year’s worth of student writing brought together as a guide or anthology. We imagine sagas taking both embodied and filmic forms. In a theatre context, the work is performed physically using techniques such as playback theatre, where scripts and improvisations are acted out by participants. Individuals might record short clips in their own environments during the week, then bring these into the shared space for improvisation. Sessions can use freeze-frame methods (either literally pausing mid-performance or pausing for reflective discussion) before building towards a final summary performance. A saga might culminate in a six-minute or eighteen-minute live presentation before an invited audience. Such performances often include a panel discussion and audience questions, which are also recorded and published alongside the saga. In filmic form, sagas may use generative AI to produce short 16-second clips stitched together with intertitles, creating a silent movie style sequence. These clips can be combined into longer episodes that preserve the group’s creative arc without requiring the physical demands of live theatre. Hybrid approaches that mix live acting and AI-generated film segments are also possible. A further dimension of the saga is the Saga Map. This is a nonlinear narrative graph that shows how scenes connect across different paths and climaxes. Users can explore the map interactively, choosing their route through the story. Each critical path can be embodied as a performance, a recorded scene, or an AI-generated clip. While 16-second video segments are currently achievable with existing tools (such as Sora 2-level generation), longer narrative arcs can also be created where technical support allows. This map can evolve into interactive theatre, interactive cinema or even a visual novel format, offering both overview and immersion. By publishing sagas at regular intervals (for example, every six weeks or every 42 elements), groups can build a guidebook of their collaborative journey. In this way, sagas transform cycles of writing and performance into structured, navigable and memorable narratives that can grow into guides, chapters and even whole volumes.
# Assets
saga-technology
# See also - Beat Technology - Scene Technology - Saga Technology