Pipelines
Pipelines
The Default phases fit a lot of music, and none of everyone’s. Beats leave the door differently than client mixes; a sample pack has no mastering phase.
A pipeline is your ordered set of workflow phases. It is the board’s source: the board renders whatever pipeline is active, so building a pipeline is building a board.
Phases in order, checklists attached
A pipeline holds up to 8 phases in order. Under each phase name sits its checklist line: the attached checklist’s name, or Attach checklist when the slot is open.
That one line is the whole binding; a phase hands its checklist to every project that enters it.
How projects join a pipeline
Projects meet pipelines at triage: a session sorts into one pipeline, and each sorted project keeps that pointer. A workspace supplies the default for new sessions.
Edits show up everywhere
Renaming, recoloring, or reordering a pipeline’s phases shows up everywhere at once; boards, cards, and pickers all read the pipeline live.
The built-in Default pipeline is code-owned and uneditable, and it is the whole story until you need more. Custom pipelines come with Studio.