Definition
A sequence of several tools arranged in order, with each step explaining "why this step is here"; the product presets dozens of them (the source of truth is knowledge/flows.yaml), and you can also assemble your own on the canvas.
In detail
A process is an ordered combination of tools, not a playbook: a playbook is the method shipped with the product (phases, gates, checklists, deliverables), while a process strings several tools into a convenient path. Preset processes have their source of truth in the repository and cannot be deleted or corrupted; self-built processes are stored in the process library. Each step of every process points to a tool that actually exists in the product; anything that cannot be pointed to is not preset. "Run through it" generates a task.
Example in practice
After receiving the task statement, the team finds 'Initiate a Project' in the process library (charter → cost → risk → schedule → create project → stand-up), fills in 'what this is for', attaches the project object, and clicks start; a task bar appears under the top bar, guiding them through all six steps page by page.