Pipelines and versions

Keep exploration editable while making every declared run reproducible.

A pipeline is a named family of versions. A version declares tasks, their order and dependencies, Spaces, prompts, parameters, and review checkpoints.

Version lifecycle

1. Create: start empty, copy a predecessor, or generate a draft.
2. Edit: inspect and change tasks, prompts, parameters, and checkpoints.
3. Declare: freeze the version.
4. Run or deploy: execute now or on a calendar schedule.
5. Iterate: create a successor from the evidence and review results.

The version catalog reports a stable public state for each entry: draft is editable and declared is frozen. Clients can therefore resume or clean up an interrupted draft without guessing from its contents or risking a declared version.

Declared versions do not change when later prompts or pipelines are edited. Sessions record what ran; they never become the authority for version ordering.

Dependencies and barriers

A task can run after every task that produces its input Spaces. Independent branches may run at the same time. Add Barrier() when later work must wait for all preceding branches even when no data dependency connects them.

Export to code

A declared version can be exported as a runner. The generated file uses public Relifold declarations and retains connected-data bindings, so it can be edited and used to register a new version.