Spaces, Flows, and Steps
A Flow is the reusable production method behind a piece of content. It can connect AI generation, media editing, assembly and review, while each Step leaves behind actual text, images, audio, video or files you can inspect and change. Run the same Flow in a fresh session for the next source; each session keeps its own inputs, drafts, edits and outputs.
A Space is a project that contains related Flows, and each card on the canvas is a Step. A node is the technical type that gives a Step its inputs, settings and output medium.
Spaces
A Space owns related Flows and their content version settings. Use separate Spaces for projects that should not share workflows or version groups.
IceFold includes five preset Studios:
- Short Video Studio for narration, animation and multi-segment video.
- Productivity Studio for PDF, meeting and scratchpad workflows.
- Media Studio for focused image, speech, music, video generation and media editing.
- Localization Studio for captioned, dubbed and voiced language versions.
- Content Repurposing Studio for turning long-form sources into channel-ready content.
Preset Flows are editable copies. Restore Studio defaults, in the Studio's … menu, replaces that Studio's changed Flows and content version settings with the current shipped defaults. Existing sessions stay unchanged.
Flows
A Flow is a directed acyclic graph used to start work. Edges connect one Step's output to named input slots on another Step. Independent branches may run concurrently.
The canvas is the Flow editor: add and remove Steps, connect inputs, arrange the graph, group selected Steps into a Subflow, or save selected Steps as another Flow. A Custom Node is authored separately when you need new behavior; turning a Flow or Subflow into one is not a save option.
Opening a Flow creates a new independent session, or restores the session you last used there. A session is the work document: it keeps its own graph, Step state, drafts and outputs. Later Flow or Studio template revisions do not silently rewrite it; existing sessions remain independent work documents.
Steps and node types
Every canvas card is a Step. Its node type defines what the Step can accept and produce. Built-in node types cover the media operations IceFold can execute directly:
- Input: text, files and multi-segment text.
- Read: audio transcription, PDF OCR and image understanding.
- Generate: text, image, speech, music and video.
- Edit: audio, image and video transforms, plus video effects.
- Compose: animated text, layered video composition and video joining.
- Extract: audio tracks and video frames.
- Subflow: package a graph behind declared inputs and outputs.
Text tasks such as translation, summarisation, re-toning and structured extraction use a Generate Text Step with a purpose-built prompt; they are not separate node types.
You can also author a custom Python node as
async def execute(inputs, ctx). Custom and Market node code runs on your
connected self-hosted runner, with the dependencies available on that machine.
Content versions
Version groups describe the content versions a project needs, such as language, platform or segment. A Step can:
- unfold a version group to produce one output per value;
- step over content versions inherited from its inputs;
- fold a version group to combine a set, such as joining segments;
- pick a tagged subset.
Each content version keeps its own output and can be rerun or pinned independently. The same Step configuration can therefore produce N coordinated content versions without copying the graph N times.
Content versions are the language, platform, segment and other forms of the work itself. They are not revisions of a Flow or Studio template: those are called template revisions, and updating one never creates another content version.